FIX: The Log Reader Agent skips some transactions when the Log Reader Agent runs to replicate transactions for a transactional replication in SQL Server 2005 and in SQL Server 2008

View products that this article applies to.

SYMPTOMS

When the Log Reader Agent runs to replicate transactions for a transactional replication in Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, the Log Reader Agent skips some transactions. This problem occurs when the following conditions are true:

A rebuild index command is running against the published database.
The rebuild index command is running in another database context.

For example, this problem occurs when you run the following statements to run the rebuild index command in the context of the master database:

USE master
GO
ALTER INDEX <Index Name> ON [<Published Database Name>].[<Article Name>]
REBUILD ;
GO

Back to the top

RESOLUTION

Service pack information for SQL Server 2005

To 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:

913089 (http://support.microsoft.com/kb/913089/ ) How to obtain the latest service pack for SQL Server 2005

Back to the top

Service pack information for SQL Server 2008

To resolve this problem, obtain the latest service pack for SQL Server 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

968382 (http://support.microsoft.com/kb/968382/ ) How to obtain the latest service pack for SQL Server 2008

Back to the top

WORKAROUND

To work around this issue, make sure that you are running the rebuild index command under the context of the published database. For example, run the following statements to run the rebuild index command in the context of the published database:

USE <Published Database Name>
GO
ALTER INDEX <Index Name> ON [<Published Database Name>].[<Article Name>]
REBUILD ;
GO

Back to the top

STATUS

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 SQL Server 2005.
This problem was first corrected in SQL Server 2008 Service Pack 1 for SQL Server 2008.

Back to the top