Database Mirroring

Database Mirroring Performance Monitoring

  • Article

Many people deploy performance monitoring solutions in a "one-size-fits-all" manner. That is, they tend to build a solution that can be easily deployed to multiple servers and capture basic information from each server. The trouble is that not every server is identical, not even within the same shop. For example, not every server may have database mirroring deployed, which means your performance monitoring solution may be missing some critical pieces of information with regards to monitoring database mirroring.


4,101 reads


The Power of Git–Getting Code


I find git to be incredibly useful, and this is a quick example of...

Daily Coping 1 Apr 2020


I’ve started to add a daily coping tip to the SQLServerCentral newsletter, which is...

SQL Homework – April 2020 – Continuity planning.


Normally for April 1st I’d try to post something a bit more lighthearted but...

Read the latest Blogs


Stored Proc slow after switching to Replication?

By jbalbo

Hi First, let me apologize in advance for my ignorance on this... We are...

update by quantity

By askcoffman

I'm writing an update statement that uses a quantity column to determine how many...

Shrinking _log file for live database

By DaveBriCam

I have a live database in SQL2016 (in Production, in use) that I need...

Visit the forum


SQL Server Q&A from the SQLServerCentral community

Get answers