Using CHAR to store UUID in SQL Server

[Zeitgeist]

Hi,

In SQL Server, I use CHAR to store UUID as primary for all my tables.

Is there any performance disadvantage when performing linking with multiple
tables? (i am concerning the indexing for CHAR field in SQL server)

Is using INT to store primary key a better way?

Thank you.

[philh]

Some folks have experienced performance problems with very large record counts
using UUID primary keys. It comes down to the size of the index, I think. Do
you really have a situation that requires more than 2.1 billion keys?

[Zeitgeist]

Not really. Just concerning the performancewhen data growing big in future.

[OldCFer]

I can't see any way that UUID's could be as efficient as integers for keys.
What are they, 35 characters
long? Most all databases have some method of producing unique integers, not
char type, for identity
(key) values.

There is a discussion of this
[url]http://www.opensourcetutorials.com/tutorials/Databases/PostgreSQL/practical-data[/url]
base-design-part-1/page2.html