I've being reading around reasons to use or not Guid
and int
.
int
is smaller, faster, easy to remember, keeps a chronological sequence. And as for Guid
, the only advantage I found is that it is unique. In which case a Guid
would be better than and int
and why?
From what I've seen, int
has no flaws except by the number limit, which in many cases are irrelevant.
Why exactly was Guid
created? I actually think it has a purpose other than serving as primary key of a simple table. (Any example of a real application using Guid
for something?)
( Guid = UniqueIdentifier ) type on SQL Server
Best Answer
This has been asked in Stack Overflow here and here.
Jeff's post explains a lot about pros and cons of using GUID.
If you are certain about performance and you are not planning to replicate or merge records, then use
int
, and set it auto increment (identity seed in SQL Server).