February 29, 2012 at 12:45 pm
Active / Active Database Geographically Disperse
I am trying to come up with a solution and not sure it is possible at all. I have a primary data center in Seattle and a DR data center in Chicago. I have been asked to look at what it would take to make the data center in Chicago active. So from a web presence I don’t have any issues… I have users that hit the Seattle DC and backend a SQL 2008 R2 database. I now want to have users that hit Chicago as well and hit a local backend database in Chicago. I need to have the two database servers have the same databases and any transactions on one updates the other… essentially meaning I have the same active database in both Seattle and Chicago.
Is this even possible?
Thinking outside of the box… is there a solution to this?
Thanks.
Jason
February 29, 2012 at 1:01 pm
Is replication an option? Either merge or transactional with updatable subscriptions?
Colleen
February 29, 2012 at 1:05 pm
I think it could be... we have about 20-30ms latency between the two sites.
February 29, 2012 at 1:16 pm
We're using updatable subscriptions with far higher latency, so that shouldn't be a problem. Do all your tables have primary keys?
February 29, 2012 at 1:17 pm
I am checking into that. I believe most have primary keys today.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply