When publishing modified pages, or performing synchronization, it is possible that you experience degrading performance during the process due to fragmented database space. Fragmented data can cause Microsoft SQL Server to perform unnecessary data reads and slow inserts of new data in the database, slowing down SQL Server’s performance.
To avoid fragmentation of the database indexes and to improve write performance and scalability of the Microsoft SQL Server, Sitefinity CMS uses sequential GUIDs for most database records’ IDs. Due to security considerations some records do not use sequential GUIDs for their IDs. For more information, see Site synchronization key.
In addition, you can rebuild the database indexes to maintain the database and optimize its performance. Thus, when a new record is inserted and needs to be put between existing records, this does not cause fragmentation of the index. This is valid especially for the clustered primary key indexes which define the physical order of the database records.
You can either automatically rebuild indexes or schedule scripts to do this on a regular basis.
NOTE: The rebuilding operation might take considerable time, depending on the size of your database.
You generally configure database optimization when you setup your system.
Back To Top