FIX: Error message when you synchronize a database or manually run sp_replcmds after you perform partial updates on a varbinary(max) column in SQL Server 2008: "The rowset does not contain any column with offset -1."

Consider the following scenario:

• You have a computer that is running Microsoft SQL Server 2008.
• You have a table that contains a varbinary(max) column.
• You set up a replication on the table.
• You perform partial updates on the column.

In this scenario, when you synchronize the database or manually run the sp_replcmds stored procedure, you may receive the following error message:

If you run the following query, you may find that the LOP_DELETE_ROWS and the LOP_INSERT_ROWS operations on the base row from the partial update are missing:

When partial updates are performed on a varbinary(max) column, SQL Server does not force an update on the base row. However, for replication, the expected behavior is that the server forces an update on the base row.

Cumulative update information

SQL Server 2008

The fix for this issue was first released in Cumulative Update 6. 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: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:

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: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. 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: Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Hotfix information

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.

Prerequisites

You must have SQL Server 2008 Service Pack 1 installed before you apply this hotfix.

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 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.

32-bit version

SQL Server 2008 Database Services Core Shared

SQL Server 2008 Database Services Core Instance

SQL Server 2008 Database Services Common Core

x64-based version

SQL Server 2008 Database Services Core Shared

SQL Server 2008 Database Services Core Instance

SQL Server 2008 Database Services Common Core

Itanium-architecture version

SQL Server 2008 Database Services Core Shared

SQL Server 2008 Database Services Core Instance

SQL Server 2008 Database Services Common Core

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

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:

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:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: