Best Practices for Speeding Up the Imports
some best practices to make the larger imports work:
- For on-premise Spira customers, on the server hosting Spira, extend the database MDF files by the approximate size of the import, so that way the database is not having to constantly expand during the import, which slows things down. If not sure the size, just extend by 10-20% of current size.
- For on-premise Spira customers, have a DBA setup an automated database full reindex every 4 hours during the import (see [KB:10] Rebuilding Database Indexes). We recommend using the script:
EXEC sp_MSforeachtable 'alter index all on ? rebuild'
- For cloud Spira customers, please log a support ticket and explain that you'll be doing the imports and that you need our hosting team to proactively increase the size of your database. They can also setup scheduled reindexes on the database during the planned migration window as well.
- To speed up some of the imports, turn off calculations for the project being imported (See: Planning - SpiraDocs). The setting to enable is "Disable Rollup Calculations". To do this, wait until the import has started and then as the import is progressing, login to Spira, locate the project being imported and change this setting. Once the project import has completed, turn this setting back off, and then run Data Tools > Refresh Test Case Cache one time to get the data back in sync.
- Before starting the import, clear the Event log inside Spira, by going to: System - SpiraDocs and click 'Clear Log'