Groups | Blog | Home
all groups > sql server replication > february 2006 >

sql server replication : Remove Identity column constraint/mgmt


dw
2/27/2006 1:40:30 PM
Hello...

We have some tables that had been using Identity columns as a Primary
Key...but we abandoned that approach a few weeks ago and adopted GUIDs
instead.

These tables are included in Publications that were originally on SQL
2000...but we upgraded to SQL 2005.

Is there a way I can remove the Identity constraint from the server
pub...does the Not for Replication handle this?

Or...would be better to Drop the column and reinitialize the subscribers?

thanks for any help
dw
2/27/2006 6:28:27 PM
Thanks for the help. I may test out going the NFR route....just so I don't
have to mess with the table schema too much. Will changing to NFR force a
Re-Init of for the subscribers?

[quoted text, click to view]
Hilary Cotter
2/27/2006 9:07:13 PM
You would be best to drop the identity column, NFR will not drop the
identity column but will not enforce the identity property if the insert is
caused by a replication process.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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]

Hilary Cotter
2/28/2006 10:49:46 AM
This is something you do on the subscriber - so for transactional
replication it will have no impact on reinitialization. For merge and
updateable subscribers it will.

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

AddThis Social Bookmark Button