Groups | Blog | Home
all groups > sql server replication > september 2005 >

sql server replication : Replication - Identity Value problem



Karthik
9/30/2005 2:59:02 AM
Hi,

I have a table with a tinyint (identity column). The current value in the
table is 2. And if I check with IDENT_CURRENT the next value is displayed as
3.

This table is an article in a merge replication. In EM if I check this
article the next value is shown as 127. And this is leading to problems in
replication. How can I get the 127 to something more manageable (say 3)?

Thank you.

Regards,
Hilary Cotter
10/3/2005 7:11:53 AM
You would be best not messing with this. However use DBCC
CheckIdent('tablename',reseed,3)

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
[quoted text, click to view]

Kurt Hill
10/6/2005 2:01:28 AM
[quoted text, click to view]

I've noticed the same thing -- on an INT identity, the value suddenly
(after 3 inserts) jumps to about 1.5 billion -- 1/2 way through the
range, it seems. Is this a bug, or a "feature"?

AddThis Social Bookmark Button