March 5, 2013 at 1:16 pm
I'm looking for a way (DMV query possibly) 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? I would like to do some performance testing in our lab.
Also, is there an easy way to see the performance overhead cost of sync compared to async?
March 5, 2013 at 3:20 pm
Database mirroring tracks (and exposes via the database mirroring monitor gui) a variety of metrics about delay, ship rate, restore rate, how far behind, etc. See books online topic on monitoring database mirroring.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
March 6, 2013 at 6:17 am
sorry I should have been more specific, I was referring to availability groups, not database mirroring
March 6, 2013 at 6:20 am
"always on" and readable secondaries is just improved database mirroring.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
March 6, 2013 at 6:37 am
Google is your friend!! Google is a friend of evrey DBA.
http://www.mssqltips.com/sqlservertip/2573/monitor-sql-server-alwayson-availability-groups/
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply