I know that having one DB would be the idea solution but opening up our internal network to the outside world (e.g. Internet) is not an option at this time due to security. Yes we have firewalls and other securities in place but it's not my decision.

Without first reading about it, do you know off hand if MSSQL handles this kind of replication rather "seamlessly" (rule-based?) or is it going to be pretty hairy implimenatation?

I'll check in to the use of ROWGUIDCOL property for pkey values. Thanks again Chris.


>Are you sure you need to have 2 separate databases, on different servers, rather than just one database and the two separate clients accessing the database? That would make things much easier :).
>
>If you do need two separate databases, you will need a ROWGUIDCOL to serves as your primary keys ROWGUIDs are unique across time and space (and therefore, your two separate databases). When one is replicated to the other, you do not need to worry about duplicate primary keys.