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
Guids are also great for offline distributed clients. AutoInc numbers will
be a thing of the past.
On Friday, May 2, 2014, Jano Petras jano.pet...@gmail.com wrote:
Hi Anthony,
Guids are easiest way forward - due to their uniqueness and native support
by the DB engine.
The only time I would
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,
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, piers.willi...@gmail.com wrote:
Probably worth saying that using guids as a
SQL Down Under | Web: http://www.sqldownunder.com/ www.sqldownunder.com
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Saturday, 3 May 2014 10:09 AM
To: ozDotNet
Subject: Re: GUIDs
I did read a web page years ago where a chap
: Saturday, May 03, 2014 10:18 AM
To: ozDotNet ozdotnet@ozdotnet.com
Subject: RE: GUIDs
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
