It is a uniqueidentifier and not string. Sent from my iPhone Stephen Russell 901.246-0159
On May 28, 2010, at 11:00 AM, "Tracy Pearson" <[email protected]> wrote: > Stephen Russell wrote on 2010-05-28: >> On Fri, May 28, 2010 at 9:54 AM, Grigore Dolghin <[email protected]> >> wrote: >>> I heard concers about speed of GUIDs versus integers. While integers >>> are indeed faster, the difference is not that big at all. >> ---------------------- >> GUID is not slower unless you are pulling tens to thousands of rows >> and then it is fractional. When you take into consideration that you >> NO LONGER need to get a reply from your insert statement about the >> new >> key you have made the cross over in faster speed usage by your users. >> IMO YMMV ;-> >> >> You can make a UDF in the db that will give you the textual data >> Customer.Name if you want so you can "see" what you wanted to see. >> > > Stephen, > > Doesn't it really depend on how you are storing the GUID? If you > convert it > to text, instead of leaving it the numeric value, it would slow > things down > more. > > Tracy Pearson > PowerChurch Software > > > > [excessive quoting removed by server] _______________________________________________ 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/[email protected] ** 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.
