all groups > sql server replication > august 2007 >
You're in the

sql server replication

group:

Primary key selection for transactional replication


Primary key selection for transactional replication Kev
8/21/2007 3:36:10 AM
sql server replication:
Hi,

We have a database with very few primary keys defined. In order to implement
transactional replication with updateable subscribers we need to define
primary keys on all tables. I need some advise as to whether it's better to
use natural primary keys or introduce artificial identity columns for
replication purposes. Or indeed whether it actually makes a huge difference
either way.

Thanks,

RE: Primary key selection for transactional replication Paul Ibison
8/21/2007 5:34:01 AM
The best thing is to post this question in the 'Programming' newsgroup. There
have been many discussions (sometimes heated!) on this before - the pros and
cons of the use of surrogate keys.
HTH,
Re: Primary key selection for transactional replication Hilary Cotter
8/21/2007 10:02:55 PM
identity keys, while being more difficult to mange in merge and queued
updating (in immediate updating they are not problematic), have the
advantage that they lead to less fragmentation than if you use naturally
occurring primary key.

--
relevantNoise - dedicated to mining blogs for business intelligence.

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