Microsoft KB Archive/927289
Article ID: 927289
Article Last Modified on 11/20/2007
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise 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 #: 50000396 (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.
This article describes the following about this hotfix release:
- The issues that are fixed by the hotfix package
- The prerequisites for installing the hotfix package
- Whether you must restart the computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
Consider the following scenario. A Microsoft SQL Server 2005 merge publication has a Microsoft SQL Server 2005 Mobile Edition (SQL Server Mobile) subscriber. In the merge publication, you create column filters on the articles of the publisher. In this scenario, updates to the SQL Server Mobile subscriber may not be reflected in the merge publication.
This problem occurs because the SQL Server Mobile subscriber does not track column version information for a vertically partitioned publication against a SQL Server subscriber.
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
- SQL Server 2005 Service Pack 1
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
You do not have to restart the computer after you apply this hotfix.
You do not have to change the registry.
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 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.
|File name||File version||File size||Date||Time||Platform|
|Mssqlsystemresource.ldf||Not Applicable||524,288||24-Oct-2006||15:52||Not Applicable|
|Mssqlsystemresource.mdf||Not Applicable||40,108,032||24-Oct-2006||15:52||Not Applicable|
|Sysdbupg.sql||Not Applicable||192,346||21-Aug-2006||15:01||Not Applicable|
To work around this problem, delete the column filters on the articles of the publisher.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The merge code on the server generates the column version information for the subscriber. Additionally, the merge code on the server calculates the absolute index for each column that is excluded. If two adjacent columns are excluded on the client, the merge code on the server may calculate the absolute index incorrectly. If the column version information that is generated is incorrect, the changes that are made to the subscriber are not propagated to the server.
This hotfix does not change SQL Server Mobile. This hotfix is a code change in the common static library in SQL Server 2005. This hotfix affects the following files:
Therefore, apply this hotfix only to SQL Server 2005. After you apply this hotfix, the merge code on the server correctly calculates the absolute index of a column if two or more adjacent columns are excluded.
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: kbtshoot kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver kbsql2005repl KB927289