Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
coolerbob
Aged Yak Warrior
841 Posts |
 Posted - 2005-06-14 : 09:22:54
|
| What is the difference between "Identity = YES" and "Identity = YES [not for replication]"?We have gone down the route of using UNIQUEIDENTIFIER GUIDs because we felt it was the best option in a replicated environment.But how well does SQL Server manage with bigint identity columns instead? Under what circumstances is it a better choice? |
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-06-15 : 03:38:31
|
| Is anyone out there working in a replicated environment? (retorical)Have you found GUID's to work better than key pools (identity not for replication)? |
 |
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2005-06-15 : 09:19:11
|
| I'm more of a developer than a DBA, so I haven't had to be directly responsible for replication. That's why I haven't responded to your question, but since there's nothing but the sound of crickets chirping here, I'll throw in my 2 cents.>>What is the difference between "Identity = YES" and "Identity = YES [not for replication]"?The difference (i believe) is that when [not for repl] is specified, the subscriber's column will not have the identity property set. (the column is still replicated) In our environment we don't write to the subscriber's so it works fine. We have no issues replicating int identity columns.Be One with the OptimizerTG |
|
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-06-15 : 12:11:40
|
| Yeah "not for replication" is like keypools in Sybase.Thats a great environment to work in. nice and simple! I wanna work there!You're right, strange why I can only hear the pins drop here. maybe too many people have asked this question in the past or something.I guess I'll just stick with guids and hope for the best. While it takes up more space (which in turn can cause performance issues on tables with many records) it sure is easier to manage! |
|
|
|
|
|
|
Identity and replication