Select the product you need help with
FIX: When you run the ALTER TRIGGER statement for a trigger in a merge publication in SQL Server 2005 or in SQL Server 2008, a change is not replicated to the subscriber databaseArticle ID: 960542 - View products that this article applies to. Bug #: 50003723 (SQL Hotfix) Microsoft distributes Microsoft SQL Server 2005 or SQL Server 2008 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 or SQL Server 2008 fix release. On This PageSYMPTOMSConsider the following scenario. In Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, you create a table in a schema. You create a trigger on the table. Next, you add the table to a merge publication as an article, and then you enable the article to replicate user triggers. Then, you run the ALTER TRIGGER statement for the trigger. In this scenario, the change is not replicated to the subscriber database. CAUSEThis issue occurs because the sp_MSmerge_altertrigger stored procedure does not include the schema name in the code where SQL Server runs the command to alter the trigger. The problematic code is as follows. RESOLUTIONCumulative update informationSQL Server 2005 Service Pack 2Important You must use this fix if you are running SQL Server 2005 Service Pack 2.The fix for this issue was first released in Cumulative Update 11 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 958735 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:
(http://support.microsoft.com/kb/958735/LN/
)
Cumulative update package 11 for SQL Server 2005 Service Pack 2937137
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.
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
SQL Server 2005 Service Pack 3Important You must use this fix if you are running SQL Server 2005 Service Pack 3.The fix for this issue was also later released in Cumulative Update 1 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 959195 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:
(http://support.microsoft.com/kb/959195/LN/
)
Cumulative update package 1 for SQL Server 2005 Service Pack 3960598 Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/960598/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was releasedSQL Server 2008The 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 2008, click the following article number to view the article in the Microsoft Knowledge Base:960484 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 2008 fix release. We recommend 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:
(http://support.microsoft.com/kb/960484/
)
Cumulative update package 3 for SQL Server 2008956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was releasedSTATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONSQL Server 2005For 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:958735
(http://support.microsoft.com/kb/958735/LN/
)
Cumulative update package 11 for SQL Server 2005 Service Pack 2SQL Server 2008For 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:960484
(http://support.microsoft.com/kb/960484/LN/
)
Cumulative update package 3 for SQL Server 2008REFERENCESFor 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 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:
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
935897 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:
(http://support.microsoft.com/kb/935897/LN/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems913089 For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/913089/LN/
)
How to obtain the latest service pack for SQL Server 2005 http://go.microsoft.com/fwlink/?LinkId=71711 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:
(http://go.microsoft.com/fwlink/?LinkId=71711)
822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/LN/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 960542 - Last Review: January 19, 2009 - Revision: 4.0 APPLIES TO
|
Back to the top
