Hello,

Correct, I do not include the brackets at all, because SQL server doesn't need them, really. I mean when a parameter is specified withouth the brackets, SQL server keeps returning the correct record. Not to mention other servers don't have this datatype at all - I implemented it as char(36).

On the other way, I see the good sides of integers. Small, compact and darn fast. But (at least in my case) I have to synchronize the data coming from 270 different local systems, so the GUID was the only way.

Thank you.

>Grigore,
>
>GUID is C(38) - I guess you miss the brackets {}. ::).
>If you like this, there are compressed forms of GUID, at least without the - signs.
>
>Why we use integers? The trick is to use a surrogate instead of the normal PK what would be normaly a string or an expression that result in a string because it is faster and you do not need that long expression on both sides of an relation. I have tables that have relations to 10 foreign tables. This will result in much bigger table then with integers.
>
>I see the good sides on GUID. I can easier transfer between databases because the record is real unique. But I guess this is not a big problem for the most of us.
>
>Agnes