Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dyckwal
Yak Posting Veteran
58 Posts |
 Posted - 2006-06-14 : 10:03:03
|
| Hello I have a table which looks like this :CREATE TABLE [INFO_EXPORT_MOVEMENT] ( [WMS_ID] [int] IDENTITY (1, 1) NOT FOR REPLICATION NOT NULL , [ItemCode] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NULL CONSTRAINT [DF_INFO_EXPORT_MOVEMENT_ItemCode] DEFAULT ('*'), [Quantity] [int] NULL CONSTRAINT [DF_INFO_EXPORT_MOVEMENT_Quantity] DEFAULT (0), [MovementDate] [datetime] NULL CONSTRAINT [DF_INFO_EXPORT_MOVEMENT_MovementDate] DEFAULT (getdate()), [MovementType] [tinyint] NULL CONSTRAINT [DF_INFO_EXPORT_MOVEMENT_MovementType] DEFAULT (0), [LocationFrom] [tinyint] NULL CONSTRAINT [DF_INFO_EXPORT_MOVEMENT_LocationFrom] DEFAULT (0), [LocationTo] [tinyint] NULL CONSTRAINT [DF_INFO_EXPORT_MOVEMENT_LocationTo] DEFAULT (0), [RefEbly] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NULL CONSTRAINT [DF_INFO_EXPORT_MOVEMENT_RefEbly] DEFAULT ('*'), [RefSupplier] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NULL CONSTRAINT [DF_INFO_EXPORT_MOVEMENT_RefSupplier] DEFAULT ('*'), [Comment] [varchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL CONSTRAINT [DF_INFO_EXPORT_MOVEMENT_Comment] DEFAULT ('*')) ON [PRIMARY]GOThe table is filled by a trigger on another table, which insert ItemCode, Quantity, MovementType, LocationFrom, LocationTo, RefEbly, RefSupplier, CommentI Have this table on 2 server running a merge subsciption. This table used to be part of this subscription, but I removed it. I stopped the merging, modified the publication on the publisher, created a new snapshot and restarted the merging.Al went ok. On the first server the WMS_ID is growing as it should be. Every record a 1 is added to previous value.On the second server however.....the WMS_ID looks like this:1210487391 KA783 69450 2006-06-14 09:51:14.380 6 3 2 0 0 3487400090000893611210487391 139 6500 2006-06-14 12:00:36.820 1 7 2 2737 00601796 3487400090000913641210487391 449 6200 2006-06-14 12:00:36.837 1 7 2 2737 00601796 3487400090000913711210487391 B6077 720 2006-06-14 13:14:45.943 1 7 2 161 3487400090000914561210487391 139 12000 2006-06-14 11:59:36.617 1 7 2 2737 00601796 3487400090000913571210487391 c509 6125 2006-06-14 11:59:36.617 1 7 2 2737 00601796 3487400090000913331210487391 139 12000 2006-06-14 11:59:36.617 1 7 2 2737 00601796 3487400090000913401210487391 A5999 690 2006-06-14 13:51:52.030 1 7 2 161 3487400090000915001210487391 KT847 73200 2006-06-14 09:54:14.787 6 3 2 0 0 3487400090000874111210487391 KT845 92400 2006-06-14 10:02:16.090 6 3 2 0 0 3487400090000880051210487391 A5999 -700 2006-06-14 13:50:51.810 1 7 2 161 348740009000091494It looks like there is still a link with the table on the first server, And that the WMS_ID is a duplicate record victim or so..I had this fenomenen also when the table was part of the replication.Does someone has any idea about this ? |
|
|
Kristen
Test
22859 Posts |
Posted - 2006-06-18 : 02:50:42
|
| Duplicate of http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=67937 |
 |
|
|
|
|
|
|
|
Problem with indentity column