>- GUID, which will be unique to each location

This option is very simple to configure, but is inefficient. Also, some client apps may not like the GUID.

>- Auto Inc + LocationID

This option is efficient, but there are important design decisions that must be made up-front.

1. What is the maximum number of subscribers you will ever, ever, ever have?
2. What are the projected number of rows that each table will contain in 2 years, 5 years, 10 years, ...?
3. Will any client apps want to use negative integers as PKs in the database?

There are a bunch of different ways to implement this, depending on your answers.

>
>
>>Hi,
>>
>>we want to use SQL Server on different locations and want to merge data, perhaps using replication.
>>
>>What would you recommend to use as primary key data type?
>>
>>Is it possible to use a INT ID field or must we use GUIDs.
>>If using guids, what kind would you recommend?
>>
>>Thanks in anvance
>>Marcus