We are looking into the possibility of using AlwaysOn Availability Groups in SQL 2014, if it works like we are hoping. What we would like to do is the following:SQL Server A: Has Primary Availability Group A with Database 1, Database 2, and Database 3. Has Secondary Availability Group B with Database 4, Database 5, and Database 6.SQL Server B. Has Primary Availability Group B with Database 4, Database 5, and Database 6. Has Secondary Availability Group A with Database 1, Database2, and Database 3.That way we could have some applications always primarily running off of SQL A and some always running off of SQL B. Our thinking is this will spread the load of the database to different servers. Questions would be"1. Can 1 server work as a Primary for one AG and as a Secondary for another AG?2. Will background transaction trying to keep everything in sync nullify what we are trying to do?3. Is there a better way to do this?I did not see any post out there actually addressing if this was possible, so sorry if this has been answered before.CheersDave
↧