• Repost - originally posted 12-06-2012

SQL Server 2012 Availability Groups Lessons Pt 7


This is the seventh tip on SQL Server 2012 availability groups (AG) to understand their configuration and setup.

Tip 7: In our current setup we have an AG with a primary and two synchronous secondaries, one for same site high availability with automatic failover, another for same site reporting. There are two databases within this AG. What we wanted to do is add another database to this AG, but it didn’t need to be highly available – it was only required for reporting. But the existing availability group is setup for two secondaries, so you need to create another AG with the primary and one secondary for reporting.

NB: This configuration may now not be required with changes made in SQL Server 2014 and 2016.

Please refer to product features for these more recent releases.


Recent Posts

See All

SQL Server 2012 Availability Groups Lessons Pt 8

This is the eighth tip on SQL Server 2012 availability groups (AG) to help you understand what else you need to consider in creating a high availability environment with AG. Tip 8: Like database mirro

SQL Server 2012 Availability Groups Lessons Pt 6

This is the sixth tip on SQL Server 2012 availability groups to make sure CDC works. Tip 6: Change Data Capture (CDC) has been around since SQL Server 2008, but now you need to incorporate CDC with SQ

SQL Server 2012 Availability Groups Lessons Pt 5

This is the fifth tip on SQL Server 2012 availability groups to make sure you get your design right. Tip 5: You are limited in SQL Server 2012 availability groups to having a maximum of two synchronou