Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

AlwaysOn Availability Groups in SQL Server 2012 Expand / Collapse
Author
Message
Posted Tuesday, March 5, 2013 1:25 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 7:52 AM
Points: 119, Visits: 544
Nice article Perry, very informative. Maybe you can help me with a question I have. I'm looking for a way (in a DMV) to see how far the secondary replica has fallen behind under heavy database load (inserts, updates, deletes) on the primary. In other words, is there a way to see how many transactions the secondary needs to apply so it is caught up and in sync with the primary?

Also, is there an easy way to measure the overhead cost of using sync compared to async?



Dustin W. Jones - Database Tech.
Post #1427025
Posted Thursday, August 8, 2013 7:35 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, October 13, 2014 3:45 AM
Points: 6, Visits: 61
How many availability groups can you have on the Primary server?

In the real world, you may have one or more associated databases that would be required to fail over as a group but that doesn't mean adding all the databases to the one group and failing them all. This is where I get a bit confused. So, can you have more than one group, on the one server, on the one WSFC node?

I am designing a possible SQL 2012 HA & DR within an WSFC and am worried about the above questions...see attachment for architecture


  Post Attachments 
DR.JPG (5 views, 97.27 KB)
Post #1482329
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse