A long time ago just down the road, no matter who asked you your name, you
always gave the same reply.
" I am Connor MacLeod of the Clan MacLeod."
DBAs, who where good at the time, where stoked. FirstName, LastName and
Clan.. Nice natural composite key.
As usual, we screwed it up, breed like rabbits and ended up doing Satan's
work. The answer now depend on who's asking...
To the telephone company I am SUCKER093546
Government I am SLAVE8273
And who is responsible for this? DBAs. They don't see people as normal
people do, they are just nodes on a B-tree and the B-Tree damn well better be as
compact as possible.
And so it came for my time in the devil's recruitment drive. Should the
identifier be an INT > 0 with the Identity property set or a GUID?
The highest weighting is given to the scope of the uniqueness for this
application. It is really the ability of a client to create a valid key
regardless of connectivity state. This is core functionality so a
If I can just get the person to have the GUID imbedded in his forehead in
Code 39 symbology, I'll get good seats for Armageddon. :-)
| posted on Friday, October 08, 2004 12:54 PM