FIX: Update of Primary Key Causes Repl Custom St. Proc to Fail

• Microsoft SQL Server, version 6.0

SYMPTOMS

On Microsoft SQL Server version 6.0, if you update the primary key of a table, the original primary key parameters passed to a custom stored procedure defined for replication will be replaced with the updated primary key values.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem was corrected in Service Pack 2 for SQL Server version 6.0. For more information, contact your primary support provider.

MORE INFORMATION

The current protocol for the definition of an UPDATE custom stored procedure is defined in the SQL Server "Administrator's Companion" under the section "Adding Stored Procedures for Insert, Update, and Delete" in Chapter 15 on Replication. According to this protocol, all column values for the updated row are passed first, followed by the original values of the primary key. If the primary key column(s) are modified in the UPDATE statement, the original primary key values are not passed correctly. Instead, the new updated primary key values are passed in their place.

Only the primary key columns actually updated will be affected. If the table has multiple primary key columns, only those referenced in the SET clause of the UPDATE statement are passed incorrectly as stored procedure parameters.