In my survey for this week, I'd like to know what you monitor if you're using database mirroring.
[Edit: The survey has closed now. See here for the results.]
I'll report on the results during the first week of February.
Thanks!
Jonathan had a client issue recently where SQL Server’s buffer pool had been forced down to a ridiculously small size, only a few hundred MB,
(This post first appeared on SQLperformance.com four years ago as part of a blog series, before that website was mothballed later in 2022 and the
One of the easiest ways to increase query performance in SQL Server is to make sure that it can quickly access the requested data, and
Spring is already in the air here in Redmond so time for March Madness! Hundreds of dollars lower-than-ever prices on our signature 158-hour Blackbelt training
In the previous Curious Case I described an issue Jonathan had at a client with very long IAM chains, and the circumstances leading to it.
(The original version of this post first appeared on the now-deleted SentryOne blog at the start of 2022.) One of the most fundamental concepts in
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.
2 thoughts on “Survey: monitoring database mirroring”
Before we had to move away from Mirroring due to "Stability under load" issues, I was monitoring the SEND, REDO queues along with Commit Overhead. Most of the monitoring was performed via extended events for when we exceeded expected maximums and interactive monitoring via the Database Mirroring Monitor.
We were configured as synchronous, automatic fail-over, and with a witness.
Robert Miller