all groups > sql server replication > june 2005 >
You're in the

sql server replication

group:

Ran out of identity range


Re: Ran out of identity range Hilary Cotter
6/27/2005 9:22:17 PM
sql server replication:
do you mean you have run out of the identity range for the datatype? If so
you have to drop the subscriptions and the publication(s) which have the
article you are interested in fixing and change the data type.

For a new subscriber, it will get a new range when you deploy the snapshot.
For an old subscription modify the replication check constraint on the table
and run a DBCC checkident reseed. Then modify the value of max_identity in
distribution.dbo.MSrepl_identity_range

I would advise you to open a support incident with PSS for this kind of
problem.

--
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]

Re: Ran out of identity range Vivek Sharma
6/28/2005 12:00:00 AM
My problem is that SQL server identity range is 2147483647 and I have
reached 2147483600. Now I have a new PC and I cannot allocate the range to
it since I am left with only 47. How do I fix the problem? One option I
have is that I export the current data to the new database with fresh
tables. Once I have done that I can recreate a new publication and then
reassign the identity range to the subscribers. Is there a better solution?


[quoted text, click to view]

Ran out of identity range Vivek Sharma
6/28/2005 12:00:00 AM
Hi,

I have ran out of indentity range and I have a new PC to add. Is there
anyway I can adjust the identity range and get to provide some identity
range to the new PC?

Thanks

Vivek

AddThis Social Bookmark Button