Indexing the History table for ClearQuest
How can I index the History table to help improve performance in IBM® Rational® ClearQuest®?
When databases become large, performance can drop for various actions.
Prior to ClearQuest 184.108.40.206, the History table is not indexed by default when creating databases. The queries run against that table can return results in a linear fashion, incrementally slowing the database over time as the size increases.
If the ClearQuest databases were created with software versions prior to 220.127.116.11, these indexes likely do not exist. To potentially increase the performance on databases, apply an index to the History table. The following is an example of SQL code used to create an index for each. This can be done with PDSQL or the vendor command line tools.
create index history_entity_idx on history (entitydef_id, entity_dbid);
This activity is available for IBM DB2®, Oracle, and Microsoft® SQL Server™. For more information on creating indexes for the back end databases, refer to your database administrator (DBA).
Always make new database back-ups of your schema repository and user databases prior to making schema changes and performing database upgrades. Failure to create back-up copies can limit your ability to recover from a an upgrade failure, design change issues or other unforeseen failures.
More support for:
Database Configuration/Connectivity - Non vendor specific
Software version: 7.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 7.0.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 7.1, 2003.06.00, 2003.06.13, 2003.06.14, 2003.06.15, 2003.06.16
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 1127710
Modified date: 28 January 2009