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.
This article has been archived. It is offered "as is" and will no longer be updated.
This article describes the following about this hotfix release:
The issues that are fixed by this hotfix package
The prerequisites for installing this hotfix package
Whether you must restart the computer after you apply this hotfix package
Whether this hotfix package is replaced by any other hotfix package
Whether you must make any registry changes after you apply this hotfix package
The files that are contained in this hotfix package
When you start a merge agent in SQL Server 2005, you experience the following symptoms:
Synchronization between the subscriber and the publisher takes a long time to be completed.
If you use SQL Server Profiler to monitor the synchronization process, you notice that the Duration column of the sp_MSmakegeneration stored procedure displays a large value after the synchronization is complete.
If you start other merge agents while the first merge agent is running, the later merge agents will not run until the sp_MSmakegeneration stored procedure that the first merge agent runs is complete.
This problem occurs when articles that the merge agent synchronizes contain join filters.
This problem occurs because the MSmerge_genhistory table contains many rows that have a value of 0 in the genstatus column.
Service pack information
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
A 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:
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.
You must have SQL Server 2005 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
You do not have to change the registry after you apply this hotfix.
Hotfix file information
This 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 the 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 version
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 1.
Triggers on the parent articles always create new rows in the MSmerge_genhistory table if the following conditions are true:
The triggers on the parent articles find any changes on the child articles.
The changes can be inserted into the MSmerge_genhistory table.
The triggers on the parent articles set the value to 0 in both the generation column and the genstatus column of the new rows.
However, you expect the triggers on the parent articles to use the existing rows in the MSmerge_genhistory table if the following conditions are true:
The existing rows reflect the changes on the child articles.
The existing rows have a value of 0 in the genstatus column.
For more information about the naming schema for Microsoft 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