Replication keeps asking for uniqueidentifier

Last Post 21 Sep 2006 08:56 AM by TRACEYSQL. 2 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
TRACEYSQL
New Member
New Member

--
21 Sep 2006 06:41 AM
We have Replication running on a live server...i just copied database...which has our updated version of erp on it and put back all primary keys on the table as the vendor does not provide this.

I go through the replication and choose transactional....I had it working then removed all the replication as they wanted another databases.....so i go back through the steps
but this time i keep getting this

But i keep getting this error
SQL Server requires that all articles in a publication allowing updatable subscriptions contain a uniqueidentifier column named 'MSrepl_tran_version' used for tracking changes to the replicated data. SQL Server will add such a column to published tables that do not have one.

Adding a new column will:
» Cause INSERT statements without column lists to fail
» Increase the size of the table

SQL Server will add a uniqueidentifier column to each of the following tables when the publication is created.

[DELTEK].[ACCT]

Its almost like SQL is thinking i choose merge replication and not transactional....

The table has Primary key on it.

if exists (select * from dbo.sysobjects where id = object_id(N'[DELTEK].[ACCT]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [DELTEK].[ACCT]
GO

CREATE TABLE [DELTEK].[ACCT] (
[ACCT_ID] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[ACTIVE_FL] [varchar] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[FY_CD_FR] [varchar] (6) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PD_NO_FR] [smallint] NULL ,
[FY_CD_TO] [varchar] (6) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PD_NO_TO] [smallint] NULL ,
[ACCT_ENTR_GRP_CD] [varchar] (6) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PROJ_REQD_FL] [varchar] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[S_ACCT_TYPE_CD] [varchar] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[DETL_FL] [varchar] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[ACCT_NAME] [varchar] (25) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[TOP_FL] [varchar] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[MODIFIED_BY] [varchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[TIME_STAMP] [datetime] NOT NULL ,
[ROWVERSION] [int] NULL ,
[L1_ACCT_NAME] [varchar] (25) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L2_ACCT_NAME] [varchar] (25) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L3_ACCT_NAME] [varchar] (25) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L4_ACCT_NAME] [varchar] (25) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L5_ACCT_NAME] [varchar] (25) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L6_ACCT_NAME] [varchar] (25) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L7_ACCT_NAME] [varchar] (25) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[LVL_NO] [smallint] NULL ,
[L1_ACCT_SEG_ID] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L2_ACCT_SEG_ID] [varchar] (13) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L3_ACCT_SEG_ID] [varchar] (11) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L4_ACCT_SEG_ID] [varchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L5_ACCT_SEG_ID] [varchar] (7) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L6_ACCT_SEG_ID] [varchar] (5) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L7_ACCT_SEG_ID] [varchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[L8_ACCT_SEG_ID] [varchar] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[TC_ACCT_TYPE_CD] [varchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY]
GO

TRACEYSQL
New Member
New Member

--
21 Sep 2006 08:56 AM
But i had this running before............transactional with primary key
and never had to put unique identifier on any of the tables.

Im confused..............i usually just select transactional then the table but now i get add unique column.

TRACEYSQL
New Member
New Member

--
21 Sep 2006 12:41 PM
I got it working but it took me all day........
It happens after you remove the entire replication all of it.

You may not use updatable subscriptions feature before, don't select it if don't need it.
(Where is this i not see it anywhere).......

As soon as i created a publication and select tables it kept coming out with the unique identifier.

I tried it twice now same thing happens then eventually it lets you do it....
You are not authorized to post a reply.

Acceptable Use Policy