Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
GUID is not an official data type in database. In our existing SQL Server design, the Uniqueidentifier type is used for GUID value. Now we are switching to Sybase database. Should we use varchar(36) to replace that Uniqueidentifier type?
I am still confused by GUID. I was told GUID is 16 bytes long but its character string is 36 characters in length. I must missed something.
A GUID is actually an integer type – it’s a 128 bit integer (16 bytes).
It’s often represented as a string of 36 characters – but the actual value is a 128bit integer value.