IDENTITY column in replicated db

IDENTITY column in replicated db

Post by FL » Fri, 11 Apr 2003 01:19:03

I have the following problem:
I'm working on a SQL db which already has some data inserted.
When a new row is inserted, the identity column doesn't get the "greatest"
but fills up the holes in the existing rows (for example if data has ID
column numbered
1,2,4,5,6,7 new row gets 3 as ID, not 8).
Can someone tell me if there's any config to change this behaviour?



1. Reuse of Replicated DB when tables have IDENTITY columns

I am using SQL Server 7.0.  I need to be able to take a
replicated DB and quickly get it up and running as
production.  The problem I am running into is that there
are many tables with IDENTITY columns.  I need to mark
these columns as IDENTITY and 'seed' the values to
something like (max(table_ID_value) + 100) I have not been
successful in coming up with the needed alter table alter
column  statement to make an existing column into an
IDENTITY.  Does this even work?  Is there another way?  
Will I have to rebuild these tables?  I want to script all
of this so it is easy to move to the new DB.  
Thanks for your help.  

2. DAO Error 3078; Need Your Help

3. Replicating Identity Columns


5. Replicate table with Identity column ins SQL 7.0

6. 3617 Error

7. Replicating with Identity columns

8. Load Testing an Informix Database

9. Cannot replicate due to Identity Column

10. Replicating DB from a target replicated DB

11. How to replicate identity columns

12. Identity columns in a replicated database

13. replicating a NEW schema with identity column