New answers tagged

3

There are certain situations where a GUID might be needed, but in general I'd advise against it. The main reason is that GUIDs are, by their nature, random. So using them as an identity column essentially means you're storing your rows randomly. With a typical incremental primary key, the data is sequential. Table scans are usually more efficient, etc. ...


1

I have seen GUID's used where there is a fear of having duplicate primary keys. This is usually seen where you have poor integration of development data into QA or SYSTEST environments. At the other end of the spectrum one Opentext application I supported only had one integer sequence which was used by every table. Voila..no duplicates! It's also used if ...


Top 50 recent answers are included