CA ERwin Model Manager Implementation Guide

Reindex the DatabaseYou should regularly reindex the database and run the database statistics.Sometimes running the database statistics alone does not affect theperformance, however it is good practice to run the database statistics on aregular basis to ensure the maximum performance of your database.In past releases, multiple versions of the same model in the mart can slowdown overall performance. You can remove versions by selectively purgingthem using the MM Version Manager. CA ERwin MM r7.2 or later lets you todisable the versioning so it does not create a new version with every save of amodel to the mart.If you have many domains in a model, they consume a lot of memory/filespace. Having too many domains can slow down both CA ERwin Data Modelerand CA ERwin MM. If you need to use many domains, we suggest you create atemplate model to house them, and then import the specific domains that youneed, to each of your individual models. If you are using the domains toenforce unique attribute or column naming standards, you can alternativelyuse the ERwin Glossary (*.nsm) for that purpose.Check the CA ERwin MM Release Notes for the latest system requirements.Greater CPU speed, and more RAM and disk space result in betterperformance.Reindex the DatabaseOver a period of time, database indexes become fragmented. A large numberof inserts and deletes can lead to significant performance degradation. Thescripts provided in this appendix rebuild the CA ERwin MM indexes and fixthem. In some cases, it can make a significant difference in the CA ERwin MMperformance.We recommend that you reindex your CA ERwin MM database nightly or duringoff-peak hours. As the index is recreated, the process can temporarily degradethe performance of your database. You can create an automated batch job todo the reindex. You should also reindex the database after a large modelmerge, a save to CA ERwin MM, and right after a conversion of the CA ERwinMM mart when upgrading to a later version of the software.70 Implementation Guide