Several of the tables in the Archive Shuttle Item Database can suffer from SQL Index Fragmentation over time. It is recommended to review this frequently during the migration and take appropriate steps. This will ensure that performance from the SQL side is optimal.
The following SQL snippet can be run to determine the amount of SQL Index Fragmentation which is present. In Archive Shuttle 6.5 and higher this information is displayed in a screen accessible by the Archive Shuttle administrator. There is also help on that screen which explains:
SELECT OBJECT_NAME(i.object_id) AS TableName, i.name AS TableIndexName, phystat.avg_fragmentation_in_percent , phystat.page_count FROM sys.dm_db_index_physical_stats(DB_ID(), NULL, NULL, NULL, 'DETAILED') phystat JOIN sys.indexes i ON i.object_id = phystat.object_id AND i.index_id = phystat.index_id WHERE phystat.avg_fragmentation_in_percent > 5 AND phystat.page_count > 1000
Screenshot of Index Fragmentation page from Archive Shuttle and information which is included in Help.
Fragmentation Corrective approach
5% – 30% Reorganize
More than 30% Rebuild (Can be achieved as online rebuild)
How to do that is written in the guide you will find here (EV10_SQL_Best_Practices_Guide.pdf / Chapter 5):