General Discussion Undecided where to post - do it here. |
Reply to Thread New Thread |
![]() |
#1 |
|
I have spent 8 hours arguing about natural keys vs surrogate keys. We talked to someone who says "You should almost always use surrogate keys for your clustered index" and then when I explained my situation, she agreed that if that was the case then natural keys are probably the better option. Although I do disagree that you should always use surrogates on your clustered index (which to me I feel it might as well be a ****ing heap, although there are reasons why that is not the case), she agreed for my situation. However, the people who were in the ****ing meeting seem to still think surrogates are best for our situation... WTF???
It's pretty obvious to me that surrogates for the clustered index is going to mean that the server is almost always going to do bookmark lookups, with every row in the lookup in a different page. Natural keys, however, will almost always mean clustered index seeks to a specific set of pages. I mean, you have 30% of the queries being seeks on the natural key, and another 60% querying a range of columns; both of which are retrieving almost every column in the table, simply because of the nature of that table. |
![]() |
![]() |
#6 |
|
|
![]() |
![]() |
#8 |
|
I tried Fat Tire once and I must say it is actually pretty darn good! I could go for one right now!!
________ WHITE WIDOW SEEDS |
![]() |
Reply to Thread New Thread |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|