On Thu, Sep 15, 2011 at 2:21 PM, Stephen Russell <[email protected]> wrote: > You will need to register to this site. > > <http://www.sqlservercentral.com/articles/Guids/75506/> > > The take away should run in any environment. > > I am still a GUID fan. I declare what they are instead of wait on the > data tier to deliver it back to me. They are just a pointer and I can > make a func() to return the usable columns of the row if I need to see > that I have the proper information.
I LOVE the idea of using GUIDs. In the current app I'm developing I took half a day and tried to change all the FKs/PKs to GUIDs. It wasn't so hard as a lot of my database code is auto-generated. With 66 tables and many keys the result was a pretty huge increase in database size, over a third bigger. In the end I wasn't comfortable and went back to using ints. However, I am using GUIDs for replication and merging. For example, I have a customer table that is replicated/merged between 2 sites. The GUID provides an ID that is unique globably and makes replication (relatively) easy. -- Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CADwx0++EvmZs5eJ0FWXCbm8RaHZOD82ZiG1wx6nz=r_iihl...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
