In general, int PKs perform faster than GUID. You do know that you can utilize the negative range and also if you expect your table to grow really large, you can use BigInit.

>Kevin,
>
>
>Beginners question...
>
>
>Are there any serious drawbacks to using a guid as a pk that you know of ?
>
>While we may get away with an int for most tables, there's one that may grow very large - if the business is successful
>
>I am thinking of making the pk of all tables guid
>
>I also want to add the possibility that someone can store a subset of the database onto his laptop, work on it, and later sync it back to the db
>
>Your opinion ?