• Repost - originally posted 17-05-2012

SQL Server 2012 Availability Groups Lessons Pt 3


This is the third tip for making your setup of SQL Server 2012 availability groups easier and complete. Tip 3: As part of a clients business requirements we are required to track every select, insert, update or delete that occurs.

We do this by using the audit functionality in SQL Server, so on our primary server we created a server audit and then in our database we created the audit specification. Now the synchronous failover server database has that audit specification but you need to create the same server audit on each server. So in this situation we had to create the server audit for each of the synchronous secondaries, one for failover and the other for reporting. By doing this you have complete auditing on failover and for reporting.


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 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 secondarie

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