Consider the following scenario:
- In Microsoft SQL Server 2008, you enable change tracking on a database. Additionally, the is_auto_cleanup_on option is enabled on the database to automatically clean up the change tracking data.
Note You can check if the is_auto_cleanup_on option is enabled or disabled by running the following query:
select * from sys.change_tracking_databases where database_id=<dbid>
- You specify the retention period for keeping change tracking information in the database by setting the CHANGE_RETENTION option.
In this scenario, you may find that after the retention period, the sys.syscommittab system table that is used by SQL Server Change Tracking grows steadily and is not cleaned up.
If you use Sync Services for ADO.NET to synchronize changes on a SQL Server 2008 database, and you enable change tracking on the database, you may encounter intermittent, slow synchronization performance because of the large size of the syscommittab table.
The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative update package 4 for SQL Server 2008 Service Pack 1
Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates