Article ID: 919949 - Last Review: November 20, 2007 - Revision: 2.5 FIX: The sp_MSinitDynamicSubscriber stored procedure is called more than one time by using the same parameters in SQL Server 2005
Bug #: 844
(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. On This PageSUMMARYThis article describes the following about this hotfix release:
SYMPTOMS Consider the following scenario. You create a merge publication that has parameterized filters in Microsoft SQL Server 2005. Then, you try to synchronize a subscriber. You use SQL Server Profiler to trace the instance of the publisher. In this scenario, the
sp_MSinitDynamicSubscriber
stored procedure is called more than one time by using the same parameters.
Note This problem may also occur when you use a SQL Server 2005 Everywhere subscriber. CAUSE This problem occurs because SQL Server calls the
sp_MSinitDynamicSubscriber
stored procedure to download all the initial data for each batch of generations. RESOLUTIONHotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites
Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel. SQL Server 2005 32-bit versionCollapse this table
SQL Server 2005 x64-based versionCollapse this table
SQL Server 2005 Itanium architecture versionCollapse this table
WORKAROUNDTo work around this problem, create a partitioned snapshot for the merge publication that has parameterized filters. For more information about how to do this, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms151260.aspx
(http://msdn2.microsoft.com/en-us/library/ms151260.aspx)
Note
In merge replication, a snapshot includes only the data from a single partition. A partitioned snapshot is used to initialize subscriptions to publications that have parameterized filters. A partitioned snapshot is known as a dynamic snapshot in earlier versions of SQL Server.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
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
(http://support.microsoft.com/kb/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
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|
Back to the top
