>Hi,
>
>For me I normally set the length only base on my estimation on how large the table probably will grow.
>The larger the lengthier, things like 10, 12, 16, 24 or even 32 chars in length.
>
>I wonder what are the key factors everyone else is considering when trying to determine the length of a GUID field (let say it is used as primary/surrogated key field of tables).
>
>Is there any good article out there discussing how should one decide the length of a GUID field (be it a sequential one or non-sequential)?

c(36) works best in my experience (but maybe because I work with SQL server a lot). Perfromance would be affected is a myth IMHO. Search for COMB keys on the internet for details explicitly related to SQL server.

Cetin