Is there any limitation of data size for using RTC with DB2?
This may be more DB2 questions but I would like to clarify this for my customer.
They are planing to register Large numbers and sizes of resources on RTC because they want to use RTC as Resource Library. They had calculated their data size to register beginning and after-time and want to confirm a few things. Their fist registration data will be 180GB, and after-time will be 120GB. The total will be around 300GB. Q1. Adding 300GB size of resources is OK for RTC and DB2? Is there any limitation of either side (RTC or DB2)? * If this is only related DB2 side, then I will check this with DB2 support. Q2. Any preparation or cautions we should take for adding large resources? such as changing some parameters on RTC server or DB2? or changing extent size of DB2? * If this is only related DB2 side, then I will check this with DB2 support. Q3. Is there any possibility that RTC can not handle too large data in the future? If this happens, then what action we need to take? such as separating data to other repository? And Dose RTC has this kind of function? Thank you, in advance. |
3 answers
This might be a good reference:
Scroll down to the DB2 section.
|
|
|
For more information on organizing data in different repositories see https://jazz.net/library/article/641. There are sizing guides for each release of Jazz. A good way to find the most up-to-date guide is site:jazz.net sizing guide in google. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.