Hi Anthony,
As part of your discovery process, you might find this CodeProject article
useful.
http://www.codeproject.com/Articles/388157/GUIDs-as-fast-primary-keys-under-multiple-database
Regards
Andrew
From: "GregAtGregLowDotCom"
Sent: Sat
Hi Greg,
I’ve never seen the point of NEWSEQUENTIALID().
It can only be used as a database default. If you’re already round-tripping to
the database, you might as well pick up an int or a big int. To me, the reason
for using GUIDs is when you want to generate the IDs in a different tier
I did read a web page years ago where a chap reported that using sequential
Guids <http://technet.microsoft.com/en-us/library/ms189786.aspx> produced
significant performance improvements -- *Greg K*
On 2 May 2014 23:56, wrote:
> Probably worth saying that using guids as a primary k
Probably worth saying that using guids as a primary key is not for everyone.
The key is bigger, so that has a size and performance impact on all your
indexes and foreign keys, and as a clustering key it means new records are
scattered throughout the file rather than being appended to the tail
Guids are also great for offline distributed clients. AutoInc numbers will
be a thing of the past.
On Friday, May 2, 2014, Jano Petras wrote:
> Hi Anthony,
>
> Guids are easiest way forward - due to their uniqueness and native support
> by the DB engine.
>
> The only time I wo
Hi Anthony,
Guids are easiest way forward - due to their uniqueness and native support
by the DB engine.
The only time I would consider using something else would be if there was a
requirement for those unique row IDs to be 64bit integers for example or if
there is a storage space concern - in
Anyone doing database replications, are you using guids? Have any
recommendations or experiences?
I don't usually use guids but working on systems that may need to scale, so
thinking of switching to guids to avoid any future scalability issues
Thanks in advance J
Anthony
