Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a performance hit if you use one data type for your primary key versus another?
I have a large database that will be queried often, but only written to once a year. Will it matter at all if I supply an incremental primary key (integer) or let SQL Server give it a GUID?
There is a performance hit, in particular with large amounts of data.
In general, use the smallest data type that will fit your needs (you can always use a larger one if needed).
When it comes to
INT(4)versusUNIQUIDENTIFIER, the former is much smaller, takes less disk space and less bytes go over the wire. This also means that indexes using such a PK will be smaller. Of course, all of this data also needs to fit in memory, so the more you can fit into memory, the better.