Guid Primary /Foreign Key dilemma SQL Server

Question

I am faced with the dilemma of changing my primary keys from int identities to Guid. I\'ll put my problem straight up. It\'s a typical Retail management app, with POS and ba

Answer 1

My take is: Use autoincrement int as PK on the inside and have a unique Guid column on each primary table that you use to move rows across databases.

Join this column when you export data, do not export the int, and map it back to int when you import data.

Especially in large volumes, int are much smaller and faster.