Article ID: 933762
Article Last Modified on 11/20/2007
APPLIES TO
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Standard 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: #50000909 (SQL Hotfix)
Bug #: 50001100 (SQL Hotfix)
Notice
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.
SUMMARY
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
SYMPTOMS
When the Log Reader Agent runs for a transactional publication in SQL Server 2005, you receive error 18815. This issue occurs if the following conditions are true:
- The transactional publication has at least one article whose schema specifies one of the following large value types:
- varchar(max)
- nvarchar(max)
- varbinary(max)
- The large value types out of row option for large value types is set to ON for the article.
Note This problem may also occur if the large value types out of row option for large value types is set to OFF for the article. The problem may occur if an update to the large value column increases the size of the column so that the large value must be stored out of row.
- The article is configured to use the XCALL command type for DELETE commands.
RESOLUTION
Update information
This hotfix is included in the cumulative hotfix package (build 3175) for SQL Server 2005 Service Pack 2 (SP2). To resolve the problem that is described in this article, install SQL Server 2005 SP2. Then, install the cumulative hotfix package (build 3175) for SQL Server 2005 SP2. 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 how to obtain the cumulative update package (build 3175) for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available
Hotfix information
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:
Prerequisites
You must have SQL Server 2005 Service Pack 1 installed to apply this hotfix. For more information about how to obtain SQL Server 2005 Service Pack 1, 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
Restart information
You do not have to restart the computer after you apply this hotfix.
Registry information
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 of 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 version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Bcp.exe | 2005.90.2226.0 | 69,488 | 19-Mar-2007 | 11:57 | x86 |
| Databasemailengine.dll | 9.0.2226.0 | 75,120 | 19-Mar-2007 | 11:57 | x86 |
| Logread.exe | 2005.90.2226.0 | 400,752 | 19-Mar-2007 | 11:58 | x86 |
| Microsoft.analysisservices.adomdclient.dll | 9.0.2226.0 | 546,160 | 19-Mar-2007 | 11:58 | x86 |
| Microsoft.analysisservices.deploymentengine.dll | 9.0.2226.0 | 140,656 | 19-Mar-2007 | 11:58 | x86 |
| Microsoft.analysisservices.dll | 9.0.2226.0 | 1,217,904 | 19-Mar-2007 | 11:58 | x86 |
| Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2226.0 | 78,192 | 19-Mar-2007 | 11:58 | x86 |
| Microsoft.sqlserver.sqlenum.dll | 9.0.2226.0 | 910,704 | 19-Mar-2007 | 11:58 | x86 |
| Msasxpress.dll | 9.0.2226.0 | 24,944 | 19-Mar-2007 | 11:58 | x86 |
| Msgprox.dll | 2005.90.2226.0 | 200,560 | 19-Mar-2007 | 11:58 | x86 |
| Msmdlocal.dll | 9.0.2226.0 | 15,646,064 | 19-Mar-2007 | 11:58 | x86 |
| Msmdredir.dll | 9.0.2226.0 | 3,993,968 | 19-Mar-2007 | 11:58 | x86 |
| Mssqlsystemresource.ldf | Not Applicable | 524,288 | 19-Mar-2007 | 09:30 | Not Applicable |
| Mssqlsystemresource.mdf | Not Applicable | 40,108,032 | 19-Mar-2007 | 09:30 | Not Applicable |
| Qrdrsvc.exe | 2005.90.2226.0 | 369,520 | 19-Mar-2007 | 11:58 | x86 |
| Rdistcom.dll | 2005.90.2226.0 | 643,440 | 19-Mar-2007 | 11:58 | x86 |
| Repldp.dll | 2005.90.2226.0 | 187,248 | 19-Mar-2007 | 11:58 | x86 |
| Replmerg.exe | 2005.90.2226.0 | 320,880 | 19-Mar-2007 | 11:58 | x86 |
| Replprov.dll | 2005.90.2226.0 | 550,256 | 19-Mar-2007 | 11:58 | x86 |
| Replrec.dll | 2005.90.2226.0 | 784,752 | 19-Mar-2007 | 11:58 | x86 |
| Replsub.dll | 2005.90.2226.0 | 407,408 | 19-Mar-2007 | 11:58 | x86 |
| Spresolv.dll | 2005.90.2226.0 | 177,008 | 19-Mar-2007 | 13:30 | x86 |
| Sqlaccess.dll | 2005.90.2226.0 | 350,576 | 19-Mar-2007 | 13:30 | x86 |
| Sqlagent90.exe | 2005.90.2226.0 | 321,392 | 19-Mar-2007 | 13:30 | x86 |
| Sqlservr.exe | 2005.90.2226.0 | 28,981,160 | 19-Mar-2007 | 13:30 | x86 |
| Sysdbupg.sql | Not Applicable | 218,486 | 29-Dec-2006 | 13:53 | Not Applicable |
| Xmlsub.dll | 2005.90.2226.0 | 195,440 | 19-Mar-2007 | 13:30 | x86 |
| Xpstar90.dll | 2005.90.2226.0 | 295,280 | 19-Mar-2007 | 13:30 | x86 |
| Xpstar90.rll | 2005.90.2226.0 | 155,504 | 19-Mar-2007 | 11:58 | x86 |
SQL Server 2005 x64-based version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Bcp.exe | 2005.90.2226.0 | 88,944 | 19-Mar-2007 | 10:53 | x64 |
| Databasemailengine.dll | 9.0.2226.0 | 75,120 | 19-Mar-2007 | 10:53 | x86 |
| Logread.exe | 2005.90.2226.0 | 525,168 | 19-Mar-2007 | 10:53 | x64 |
| Microsoft.analysisservices.adomdclient.dll | 9.0.2226.0 | 546,160 | 19-Mar-2007 | 10:53 | x86 |
| Microsoft.analysisservices.adomdclient.dll | 9.0.2226.0 | 546,160 | 19-Mar-2007 | 11:58 | x86 |
| Microsoft.analysisservices.deploymentengine.dll | 9.0.2226.0 | 140,656 | 19-Mar-2007 | 11:58 | x86 |
| Microsoft.analysisservices.dll | 9.0.2226.0 | 1,217,904 | 19-Mar-2007 | 11:58 | x86 |
| Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2226.0 | 94,064 | 19-Mar-2007 | 10:53 | x64 |
| Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2226.0 | 78,192 | 19-Mar-2007 | 11:58 | x86 |
| Microsoft.sqlserver.sqlenum.dll | 9.0.2226.0 | 877,936 | 19-Mar-2007 | 10:53 | x86 |
| Msasxpress.dll | 9.0.2226.0 | 30,064 | 19-Mar-2007 | 10:53 | x64 |
| Msasxpress.dll | 9.0.2226.0 | 24,944 | 19-Mar-2007 | 11:58 | x86 |
| Msgprox.dll | 2005.90.2226.0 | 262,000 | 19-Mar-2007 | 10:53 | x64 |
| Msmdlocal.dll | 9.0.2226.0 | 15,646,064 | 19-Mar-2007 | 11:58 | x86 |
| Msmdredir.dll | 9.0.2226.0 | 3,993,968 | 19-Mar-2007 | 11:58 | x86 |
| Mssqlsystemresource.ldf | Not Applicable | 524,288 | 19-Mar-2007 | 09:30 | Not Applicable |
| Mssqlsystemresource.mdf | Not Applicable | 40,108,032 | 19-Mar-2007 | 09:30 | Not Applicable |
| qrdrsvc.exe | 2005.90.2226.0 | 434,032 | 19-Mar-2007 | 10:53 | x64 |
| rdistcom.dll | 2005.90.2226.0 | 836,464 | 19-Mar-2007 | 10:53 | x64 |
| Repldp.dll | 2005.90.2226.0 | 237,936 | 19-Mar-2007 | 10:53 | x64 |
| Repldp.dll | 2005.90.2226.0 | 187,248 | 19-Mar-2007 | 11:58 | x86 |
| Replmerg.exe | 2005.90.2226.0 | 417,648 | 19-Mar-2007 | 10:53 | x64 |
| Replprov.dll | 2005.90.2226.0 | 747,888 | 19-Mar-2007 | 10:54 | x64 |
| Replrec.dll | 2005.90.2226.0 | 1,011,056 | 19-Mar-2007 | 10:54 | x64 |
| Replsub.dll | 2005.90.2226.0 | 528,240 | 19-Mar-2007 | 10:54 | x64 |
| spresolv.dll | 2005.90.2226.0 | 225,648 | 19-Mar-2007 | 10:54 | x64 |
| Sqlaccess.dll | 2005.90.2226.0 | 357,744 | 19-Mar-2007 | 10:54 | x86 |
| Sqlagent90.exe | 2005.90.2226.0 | 392,560 | 19-Mar-2007 | 10:54 | x64 |
| Sqlservr.exe | 2005.90.2226.0 | 39,368,048 | 19-Mar-2007 | 10:54 | x64 |
| Sysdbupg.sql | Not Applicable | 218,486 | 29-Dec-2006 | 13:53 | Not Applicable |
| Xmlsub.dll | 2005.90.2226.0 | 319,856 | 19-Mar-2007 | 10:54 | x64 |
| Xpstar90.dll | 2005.90.2226.0 | 543,600 | 19-Mar-2007 | 10:54 | x64 |
| Xpstar90.rll | 2005.90.2226.0 | 156,016 | 19-Mar-2007 | 10:54 | x64 |
WORKAROUND
To work around this issue, change the DELETE command type that is configured for the article from XCALL to CALL.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
When an article is configured to use the CALL command syntax for DELETE commands, only the primary key of the row that you want to delete is passed to the delete procedure. When an article is configured to use the XCALL command syntax for DELETE commands, the original values for all the columns that are defined in the article are passed to the delete procedure.
For more information about the different syntax options that each Data Manipulation Language (DML) command type supports, see the "Specifying How Changes Are Propagated for Transactional Articles" topic in SQL Server 2005 Books Online. 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: kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver kbsql2005repl KB933762
