A few more questions.
Is there common data between the two databases that needs to be in sync? Or, is this data completely separate?
If there is data that needs to be synced, does some of it need to be real time, and some of it can be synced on a schedule? This may simplify things.
Are these servers in the same domain, or, trusted domains? Or are they completely separate boxes? The VPN question makes me think that there is no physical connection between these servers.
Why do the different databases need to be in two different countries? If this is a web app, there is nothing stopping you from having these databases in the same physical location. They can even be on the same server.
I had a similar situation where the application and database lived in the United States, and the application users were in China. The original plan was to implement a second server and bi-directional transactional replication. We threw that out, and had the users in China connect directly to the app in the US. We then implemented transactional replication as well as snapshot replication from the US to China. A separate "read only utility" application was created so that the China users could read the replicated data instead of pulling significant amounts of data over the VPN connection.
Jeff's suggestion to use this as an opportunity to implement DR should also be taken into consideration. Some higher level assistance will likely be required.
Michael L JohnIf you assassinate a DBA, would you pull a trigger?
To properly post on a forum:http://www.sqlservercentral.com/articles/61537/