>What happens when you want to introduce another site (read "database") into the replication scheme?
That's just it Michael, I don't know since I haven't even yet tested the implementation and I have no experience with MSSQL replication. I want to know the "best" approach before I deploy it so that I don't have to make a lot of adjustments after a rollout.

>What about introducing a site id and making the PK a composite of the site id and the IDENTITY?
This solution I know of because I have experience deploying it but only under Foxpro. Because Foxpro wasn't built to handle replication, it was a messy solution of program logic to handle it. Personally, it was a nightmare making sure everything synced correctly.

I know MSSQL handles replications much cleanly but I just don't know enough about it to set it up correctly for seamless replication.