r15 - 2019-10-03 - 11:58:17 - PaulEllisYou are here: TWiki >  Deployment Web > DeploymentPlanningAndDesign > DatabaseGrowth

Database Growth - Strategies for minimizing the growth of repository databases new.png

Authors: RosaNaranjo
Build basis: None

In planning or maintaining your CLM deployment, you may ask yourself these questions: "How do I ensure that my database size will not spiral out of control?", "Are there any strategies I can put in place to help with this in the beginning?", "Are there objects I should avoid storing in my repository?". There are some recommendations that will be captured in this page as well as some links to content that will help you understand <...>

Engineering Workflow Management/Rational Team Concert

In Engineering Workflow Management, formerly Rational Team Concert, there are several items that can contribute greatly to database growth if not kept in check. These items are build results, workitem attachments, and binary content in SCM as versioned content. There are several articles and presentations that have been written on this topic.

Engineering Test Management/Rational Quality Manager

For QM, there are some usages that can drive repository db growth. For example, automations generating Execution Results and attachments on the test artifacts such as HTML, images, etc. attached to either scripts or results. QM does have some ability to permanently delete content. See Deletion and restoration of test artifacts.

DOORS Next Generation

The "safest" way to reduce DB size is to archive projects and use the repotools -deleteJFSResources command Note that this can have consequences, for example, what if you have cross project links from other projects?. You can also run that command against unarchived projects to clean up artifacts in that project which have been deleted, but that may affect baselines and history that may be important.

One thing changed between 5.x and 6.x though, which is you can no longer run deleteJFSResources without the "force" parameter which deletes everything in the specified project. This is due to the way resources are unmapped versus archived, so running without "force" in 6.x seems to not find anything to delete. Otherwise, there is one other task, com.ibm.team.jfs.indexing.service.internal.CompactIndexesTask that can be scheduled daily/weekly to help manage the index size. See this page for details.

Deleting data permanently from a DOORS Next Generation project

UPDATE: Prior to DOORS Next Generation 6.0.6, this task should NOT be enabled, com.ibm.team.jfs.indexing.service.internal.CleanUpUnusedIndexesVersionsTask See CleanUpUnusedIndexesVersionsTask incorrectly cleans up versions still in use defect for details.
If you are using 6.0.6, then the task is automatically set to run daily. See the following guidance issued on this task and the related repair command.

  1. OutOfMemoryException errors and performance degradation caused by the CleanUpUnusedReferences task for DOORS Next Generation
    ii. Upgrading DOORS Next Generation to 6.0.6 requires that repairUnreferencedVersions is run before running a reindex

The CleanUpUnusedIndexesVersionsTask is an important part of maintaining a reduced index size and optimize DNG performance. The guidance above will allow you to utilise this daily feature.

Data Warehouse

Data warehouse database size is huge and growing fast

Jazz.net forum resources

The forum contains many good suggestions from CLM Administrators who are maintaining CLM deployments.

Question: I want to store binaries in RTC. Does RTC SCM support delta compression?

Answer: Yes. RTC SCM supports delta compression of files, including binary files. In fact, one of the properties you can change in advanced properties is whether to enable or disable delta compression. If delta compression results in larger gains than other compression types it will be used to compress a given binary.

Question: Can I prevent binaries from being checked-in to RTC?

Answer: Yes, you can implement file limits in RTC.

Question:Does RTC store all versioned elements in the database?

Answer:Yes, RTC-SCM stores all versioned elements in the database.

Question:What can I do to monitor db growth and what does RTC do on its own?


  • RTC will run item cleanups daily (sometimes frequently throughout the day) to help clean stale data. You can investigate increasing this task, or the expiration time of these items (located in Advanced Properties)
  • You can also run the onlineverify to ensure the consistency of the data and that there is no corruption which may be preventing the item clean up from running.
  • ensure all your builds are being pruned and any results cleaned up

Question How can you scrub ChangeEvents from the repository database using IBM Rational Team Concert?

Answer http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21390701









expected database growth when versioning binary data

Versioning binary artifacts

Related topics: Deployment Planning and Design, Why is my database consuming so many resources?

Additional contributors: TimFeeney, StefVanDijk, BenjaminSilverman, KrzysztofKazmierczyk

Topic attachments
I Attachment Action Size Date Who Comment
Gifgif RDNG.gif manage 18.2 K 2016-07-07 - 17:21 RosaNaranjo  
Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r15 < r14 < r13 < r12 < r11 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
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.