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 |
|
abdul
Starting Member
28 Posts |
 Posted - 2006-09-13 : 04:11:06
|
| I'm using merge replication between two machines. Most of the tables have their own primary key columns and sql server automatically puts "rowguid" column to every table. As far as I know it should not do that, am I wrong? I wonder if I can get rid of "rowguid" column on the tables which already have primary key column. Thanks a lot...abdul |
|
|
harsh_athalye
Master Smack Fu Yak Hacker
5581 Posts |
Posted - 2006-09-13 : 04:21:16
|
| ROWGUID column is required for merge replication, you can't skip it...Another thing is that it has nothing to do with primary keys or domain integrity. As far as I know, the ROWGUID column is required for versioning of rows so that while replicating rows SQL server can understand which rows are changed since last replication.Harsh AthalyeIndia."Nothing is Impossible" |
 |
|
|
abdul
Starting Member
28 Posts |
Posted - 2006-09-13 : 04:22:34
|
| Harsh thanks a lot. That's all I needed. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-09-13 : 04:28:33
|
| No doubt obvious, but if you already have a GUID in any of your tables (either as a PK or as a unique reference) you can double that up with the ROWGUID by adding the ROWGUIDCOL property to your existing GUID column.You ought to have a Unique Index on the column (representing ROWGUID) tooKristen |
|
|
|
abdul
Starting Member
28 Posts |
Posted - 2006-09-13 : 10:03:15
|
| and Kristen thank you too for enlightning :D |
|
|
|
|
|
|
Why "rowguid" and can I get rid of it?