I've read several different replication scenarios and technologies native to SQL Server (we are talking about SQL Server 2005) but have some questions.
I have a project to integrate/replicate two network-separated SQL Server 2005 databases. Each database resides in a physically separate location at different companies. They will not have a shared network environment and will not allow direct
connection between the two databases.
We need to keep each database in sync as far as customer records. Near real time is preferable. There is not master. One could add/delete/modify a customer record in one database and it needs to reflect in the other database.
The closest we could get for connectivity architecture looks like this:
1. Each database is on the separate internal networks for each company.
2. Each organization HAS agreed to setup a DMZ on their sides specifically for this exchange. Each respective DMZ will be able to communicate with their own internal SQL Server and have a fiber connect directly connecting each organization's
SO.... is there a good way to replicate from InternalSQL_1 - DMZ1 - DMZ2 - InternalSQL_2 near real time?
What would your recommendation be? Pretty sure I'd setup both internal InternalSQL as Pub/Sub/Dist but I'm solici
View Complete Post