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 |
|
mrtaikandi
Starting Member
1 Post |
 Posted - 2014-09-26 : 03:30:12
|
| Based on [url]http://stackoverflow.com/questions/11938044/what-are-the-best-practices-for-using-a-guid-as-a-primary-key-specifically-rega[/url] question on StackOverflow, IMHO if you use sequential GUID as PK with non-clustered index and use a INT or BIG INT IDENTITY as clustered index and considering that the app might later require replication, it would be beneficial and wouldn't have that much performance lost in table scans, inner joins and inserts.But what about the may to many relations? Should we also use a different (INT or BIGINT) clustered index for their bridge table to gain the same performance as bridge tables with BIGINT FKs? |
|
|
|
|
|
Using Sequential GUID in many to many relations in