I'm testing possible solutions for database redundancy and high availability.
My objective is to have various applications working simultaneous and communicating with one database only. But having the databases synchronized between them so that in case of one database goes down, all its data is not lost. ![Desired architecture]
How can I do this in order that all databases are publishers/subscribers and for a commit to be done, must be done in all databases (a two-phase commit protocol between all databases "online")? : http://i.stack.imgur.com/N8Jhb.gif
asked Dec 02, 2011 at 10:17 AM in Default
You've tagged this question with SQL2008, but can you wait until SQL2012 is released? There's a feature called AlwaysOn, that will fit your requirements quite well : http://www.microsoft.com/sqlserver/en/us/future-editions/mission-critical/SQL-Server-2012-high-availability.aspx
This combines the 2 technologies of mirroring (to give multiple copies of the data) and clustering (to give seamless failover). A good introduction can be found here : http://blogs.technet.com/b/andrew/archive/2011/11/15/sql-server-2012-always-on.aspx
answered Dec 03, 2011 at 05:53 AM
Kev Riley ♦♦