The .SQLITE model database file is extremely large, even for a model with a reasonable number of elements and alternatives. For example 6 GB for a 7000 pipe model. This may make performance very sluggish and take a long time to open and save.
First, check if you have Change Tracking enabled. This is located under the Review menu. Click Change Tracking and see if the box is checked next to "Track Changes". If so, choose "view tracked changes" and check the number of records. If it is large (for example millions of rows), this can cause the database file to be very large and reduce performance especially when opening and saving the model. This could be caused by performing bulk operations such as ModelBuilder imports and constraint based design runs. These types of operations can result in a large number of extra rows of data in the change tracking system (sometimes tens of millions of rows).
Starting with version 10.03.01.08 (and greater), you can now archive change tracking data in both the water and storm-sewer products. This can help with situations where including change tracking data may otherwise increase the size of the model's database file to a great extent.
In addition, a Bulk Archive features was added in the CONNECT Edition Update 4 release (10.04.00.XXX). With this, you will be able to archive a large number of items from the Change Tracking database. This will remove the items from the model database file and store the archived changes in an external database file.
You can access this by going to the Review tab, click "Bulk Archive." You can choose how many records to keep or delete all change tracking data. After performing the Bulk Archine, it is recommended to compact the database.
Note: This does not replace the Archive feature in the Change Tracking manager.
For more information, see the section "Removing / clearing change tracking records" in the following article: Using Change Tracking for insights into model changes
"Archive remaining records" means it will save a .sqlite file with the change tracking records, for backup purposes. If you do not need this, choose "Delete remaining records" which will remove them.
If you simply want to remove all change tracking records, set the “records to keep” to zero and choose "Delete remaining". Perform a database compact (File > Database Utilities > Compact) after doing this, to free up the space. Consider turning off Change Tracking (from the Review menu) if you do not wish to continue accumulating more change tracking records.
Another way to reduce the size of the database is to try compacting the database and purging records to save space, in case old records of previously removed elements and components are still stored in the database. This is done by opening the product without opening any models, then going to File > Database Utilities > Compact Database > Select Model > choose the Purge option. (Note: if you utilize the GIS-ID feature, you may need to purge additional elements from the "GIS-ID Center for Deleted Elements" - see this article for more)
If you are using an older version of the software, you can use the below information to manually clean up the change tracking database using the below information, or contact Technical Support (for example post in the Forum) to manually remove the information from the database.
Note: the following information is for advanced users who are comfortable with directly editing the model database. Care should be taken to back up your model before performing these steps. If in doubt, contact Technical Support.
Using Change Tracking
Compacting a database for optimal performance and general troubleshooting