Must declare the scalar variable "@Variable".
- The transactional replication contains a created article that is based on a table that has computed columns.
- The primary key column is sorted after the computed columns are sorted.
- From the syscolumns system table, you can see that the column ID of the primary key column is larger than column IDs of the computed columns.
- The publication uses concurrent snapshot processing.
Cumulative update informationThe fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
- When you create the underlying table of the article, make sure that the primary key column is sorted before the computed columns are sorted.
- Use native snapshot processing or database snapshot processing instead of concurrent snapshot processing.
CREATE TABLE [dbo].[test](
[col1] [char](10) NOT NULL,
[col2] [char](10) NOT NULL,
[col_1_2] AS ([col1] + [col2]),
[ID] [int] IDENTITY(1,1) NOT FOR REPLICATION PRIMARY KEY NOT NULL
Article ID: 936534 - Last Review: Oct 8, 2011 - Revision: 1