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!
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
Last month I was looking for the spinlocks whitepaper and discovered that both it and the latches whitepaper had disappeared from the Microsoft website. I
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
Since my first round of community mentoring back in 2015, when I mentored 54 people for six months, I’ve been asked periodically whether I’d do
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