Article ID: 938675
Article Last Modified on 6/20/2007
APPLIES TO
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Standard 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
Bug #: 50001288 (SQL Hotfix)
SYMPTOMS
You have a transactional publication in Microsoft SQL Server 2005. The update on the subscribers may take longer time to complete than when you perform the same operation in Microsoft SQL Server 2000. This problem occurs if the following conditions are true:
- The transactional publication has immediate updating subscriptions enabled.
- You set the @identityrangemanagementoption option to auto when you run the sp_addarticle stored procedure.
Or, if you use SQL Server 2005 Management Studio to add articles for the transactional publication, you set the Automatically manage Identity ranges article property to Automatic.
CAUSE
This problem occurs because of behavior that occurs when the IDENTITY property is set on the published table schema. In this case, SQL Server 2005 does not cache the execution plan for the synchronization update stored procedure that is called by the subscriber at the publisher. For example, the stored procedure name that is called at the publisher server is sp_MSsync_upd_ACCOUNT_1. SQL Server 2005 compiles the stored procedure for every row update on the subscriber. Therefore, the overall elapsed time for the update increases.
RESOLUTION
Cumulative update information
To resolve this problem, obtain the cumulative update package (build 3175) for SQL Server 2005 SP2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available
WORKAROUND
To work around this problem, use one of the following methods:
- Avoid large single transaction updates on the subscribers.
- If you run the sp_addarticle stored procedure to add articles for a transactional publication, do not set the @identityrangemanagementoption option to auto.
If you use SQL Server 2005 Management Studio to add articles for a transactional publication, do not set the Automatically manage Identity ranges article property to Automatic.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Keywords: kbpubtypekc kbqfe kbfix kbexpertiseadvanced kbsql2005repl KB938675
