Article ID: 938363
Article Last Modified on 8/30/2007
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Workgroup Edition
Bug: #50001367 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
SYMPTOMS
Consider the following scenario. You set up a merge replication in Microsoft SQL Server 2005. Then, you create different partitions to be sent to different subscribers by using parameterized row filters. When you synchronize a subscriber, some data is not replicated to the subscriber.
For example, in this scenario, the following conditions are true:
- You have two publications that both contain articles that are named article A and article B.
- You create a join filter for article A and for article B for each publication.
- Article A is the parent article. Article B is the child article.
- You create different parameterized row filters for the two publications. The two publications are named publication A and publication B.
- The two parameterized row filters define different partitions. The two partitions are named partition A and partition B.
- You create two subscribers for the two publications. The two subscribers are named subscriber A and subscriber B.
In this scenario, you perform the following operations:
- On subscriber A, you update a record to change the data that is to be included in partition B.
- You synchronize the change from subscriber A to the publisher.
- You synchronize the data from the publisher to subscriber B.
After you complete these operations, you may notice that the data is not replicated to subscriber B.
RESOLUTION
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2
Note 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 2005 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:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
After you apply this hotfix, you must stop all the synchronization activities both at the publisher and at the subscriber. Then, you must run the sp_vupgrade_mergeobjects stored procedure against the publication database to regenerate the INSERT trigger, the UPDATE trigger, and the DELETE trigger.
For more information about the sp_vupgrade_mergeobjects stored procedure, visit the following Microsoft Developer Network (MDSN) Web site:
http://msdn2.microsoft.com/en-us/library/bb326615.aspx
For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2
REFERENCES
For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
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:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 2, 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
For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
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:
822499 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:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbsql2005repl kbhotfixrollup kbfix kbpubtypekc kbqfe kbexpertiseadvanced kbhotfixserver KB938363
