To attach or not to attach...
Hello
Our company sells an Eclipse-RCP based product. Whenever the product
encounters a critical error, it sums up some log files and a data
excerpt in a ZIP, and prepares an E-Mail for QA. The mail has the ZIP
attached to it. As the ZIP can be sent by mail, its size varies between
2 MB up to 20 MB.
Internally we use RTC Express with a DB2 Express on a mid-size machine.
(2 GB RAM, C2D with 2.4 GHz, HDD size sufficient).
Whenever we get such a mail, we open a WI and assign the QA request the
WI number. Now we have two options: either we store the ZIP one the
filesystem (name would be WI-number + date of reception) or we add the
ZIP as attachment to the WI.
Would you recommend to store the data externally? Or can we add the ZIP
to the DB without worries? As the data would accumulate over the years
to an impressive amount, we wonder whether our DB2 and Jazz repo can
handle it. Or whether you recommend to store such data outside the
repository.
Thanks,
Stefan Stern
Our company sells an Eclipse-RCP based product. Whenever the product
encounters a critical error, it sums up some log files and a data
excerpt in a ZIP, and prepares an E-Mail for QA. The mail has the ZIP
attached to it. As the ZIP can be sent by mail, its size varies between
2 MB up to 20 MB.
Internally we use RTC Express with a DB2 Express on a mid-size machine.
(2 GB RAM, C2D with 2.4 GHz, HDD size sufficient).
Whenever we get such a mail, we open a WI and assign the QA request the
WI number. Now we have two options: either we store the ZIP one the
filesystem (name would be WI-number + date of reception) or we add the
ZIP as attachment to the WI.
Would you recommend to store the data externally? Or can we add the ZIP
to the DB without worries? As the data would accumulate over the years
to an impressive amount, we wonder whether our DB2 and Jazz repo can
handle it. Or whether you recommend to store such data outside the
repository.
Thanks,
Stefan Stern
One answer
Generally it should be okay to store medium sized attachments in the
repository. Some other determining factors you should ask:
- Do you expect there to be a very large number of these attachments, or is
it occasional?
- Do you expect to retain these attachments permanently?
Today storage of attachments in RTC is permanent - there is not a feature to
remove them, so the integrity of the work item links is preserved. So if
you wish to prune files then external storage would provide you more
flexibility.
For one reference point, the Jazz development repository has grown to an ~60
GB database on db2.
--
Ritchie Schacher
Jazz Server Development
"Stefan Stern" <Stefan> wrote in message
news:gplf64$fod$1@localhost.localdomain...
repository. Some other determining factors you should ask:
- Do you expect there to be a very large number of these attachments, or is
it occasional?
- Do you expect to retain these attachments permanently?
Today storage of attachments in RTC is permanent - there is not a feature to
remove them, so the integrity of the work item links is preserved. So if
you wish to prune files then external storage would provide you more
flexibility.
For one reference point, the Jazz development repository has grown to an ~60
GB database on db2.
--
Ritchie Schacher
Jazz Server Development
"Stefan Stern" <Stefan> wrote in message
news:gplf64$fod$1@localhost.localdomain...
Hello
Our company sells an Eclipse-RCP based product. Whenever the product
encounters a critical error, it sums up some log files and a data excerpt
in a ZIP, and prepares an E-Mail for QA. The mail has the ZIP attached to
it. As the ZIP can be sent by mail, its size varies between 2 MB up to 20
MB.
Internally we use RTC Express with a DB2 Express on a mid-size machine. (2
GB RAM, C2D with 2.4 GHz, HDD size sufficient).
Whenever we get such a mail, we open a WI and assign the QA request the WI
number. Now we have two options: either we store the ZIP one the
filesystem (name would be WI-number + date of reception) or we add the ZIP
as attachment to the WI.
Would you recommend to store the data externally? Or can we add the ZIP to
the DB without worries? As the data would accumulate over the years to an
impressive amount, we wonder whether our DB2 and Jazz repo can handle it.
Or whether you recommend to store such data outside the repository.
Thanks,
Stefan Stern