You are currently offline, waiting for your internet to reconnect

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

Extended support for SQL Server 2005 ended on April 12, 2016

If you are still running SQL Server 2005, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

This article has been archived. It is offered "as is" and will no longer be updated.
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 masterGOALTER INDEX <Index Name> ON [<Published Database Name>].[<Article Name>]REBUILD ;GO
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 How to obtain the latest service pack for SQL Server 2005

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:
968382How to obtain the latest service pack for SQL Server 2008
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>GOALTER INDEX <Index Name> ON [<Published Database Name>].[<Article Name>]REBUILD ;GO
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.
More information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 959001 - Last Review: 01/16/2015 08:16:00 - Revision: 3.0

Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Standard X64 Edition, Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems, Microsoft SQL Server 2005 Enterprise X64 Edition, Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems, Microsoft SQL Server 2005 Workgroup Edition, Microsoft SQL Server 2008 Developer, Microsoft SQL Server 2008 Enterprise, Microsoft SQL Server 2008 Standard, Microsoft SQL Server 2008 Web, Microsoft SQL Server 2008 Workgroup

  • kbnosurvey kbarchive kbsql2005repl kbtshoot kbexpertiseadvanced kbfix KB959001
Feedback