Article ID: 959012 - View products that this article applies to.
Consider the following two scenarios in Microsoft SQL Server 2005:
When you shrink the database or the Ghost Cleanup process runs, forwarded versioned records in a heap are not handled correctly. Therefore, the Ghost Cleanup process skips these records, and the Ghost Cleanup transaction rolls back. Because Ghost Cleanup will try to execute the transaction again and then roll back repeatedly, the transaction log grows. In addition, because Ghost Cleanup does not delete records, you cannot shrink the database, and the database grows continuously. Therefore, you have less disk space.
Service pack informationTo resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/913089/ )How to obtain the latest service pack for SQL Server 2005
To work around this issue, you can create a clustered index on the table. Then, you can drop the clustered index.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in SQL Server 2005 Service Pack 3.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 959012 - Last Review: November 9, 2010 - Revision: 3.0