Hi
What impact is there in setting a unqiueidentifier primary key to be a row guid?
How does this impact performance?
How does this impact data file size?
Does it impact anything else?
Thanks
Hi,I guess you don′t want to open up taht religious discussion, right ? There were many, many, many discussions already about this out there which can be find googling / MSNning around:
http://www.google.de/search?hl=de&q=GUID+Primary+Key&meta=
There are really many opinions out there, for me (for my personal opinion) you should avoid them, as long as you don′t really need them, like for distributed applications)
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
Hi Jens
Thanks for the response but I wasn't asking if I should use a UNIQUEIDENTIFIER as a primary key.
I was just wondering what the impact was in setting the rowguid flag.
For example...
CREATE TABLE Schema.Table (Id UNIQUEIDENTIFIER ROWGUIDCOL NOT NULL CONSTRAINT PTableId PRIMARY KEY NONCLUSTERED WITH FILLFACTOR=60)
CREATE TABLE Schema.Table (Id UNIQUEIDENTIFIER NOT NULL CONSTRAINT PTableId PRIMARY KEY NONCLUSTERED WITH FILLFACTOR=60)
sql
No comments:
Post a Comment