In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-19 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
SQL Server database mirroring key performance counters
There are basically five ways to monitor database mirroring:
1. Configure database mirroring monitor and set alarm threshold.
two。 Configure WMI EVENT ALERT to configure actions or alarms after the image status is modified.
3. Use the system Monitor to view key performance counters.
4. The deployment job monitors the abnormal image status and sends alarms.
5. Use sp_dbmmonitorresults to get mirrored data.
Of course, database mirroring state changes in database events can also be monitored using extended events and SQL Server Profiler. This tool is mainly used for tracking, rather than the conventional means of monitoring.
This blog post focuses on how to use system Monitor (formerly known as performance Monitor) to monitor database mirroring performance. The SQL Server:Database Mirroring object contains performance counters for database mirroring. The following list describes some key counters.
Key master server counters:
Log Bytes Send/sec: the transfer rate of logs from master to mirror
Log Send Queue KB: the total number of logs that have not been sent to the mirror (in kilobytes)
Transaction Delay: the delay (in milliseconds) spent waiting for a reply from the mirror submission. This counter is useful for determining whether database mirroring on the primary server affects performance.
Log Compress Bytes Sent/sec: the compressed byte size of the log sent in the last second. To calculate the log compression ratio, you can use Log Compressed Bytes Sent/sec divided by Log Bytes Sent/sec.
Log Bytes Sent from Cache/sec: the number of send log bytes obtained from the mirror log cache in the last second. This counter is used only on the principal server. This value is always 0 on the mirror server.
Key mirror server counters:
Redo Bytes/sec: the rate at which logs are rolled forward in the mirror database.
Redo Queue KB: there is no total number of logs rolled forward to the mirror database. (in kilobytes) to evaluate the time it takes for a mirror to redo the log, you can divide Redo Queue KB by Redo Bytes/sec.
Log Bytes Received/sec: the rate of logs received from the master. To evaluate how long the mirror will take to catch up with the master, you can divide Log Send Queue KB by Log Bytes Received/sec.
Log Compressed Bytes Received/sec: the size of the compressed log received in the last second.
Log Bytes Redone from Cache/sec: the number of redo log bytes obtained from the mirror log cache in the last second. This counter is used only on the mirror server. This value is always 0 on the principal server.
Use performance counters to monitor database mirroring performance. For example, you can check Transaction Delay counters to determine whether database mirroring affects the performance of the principal server, and you can check Redo Queue and Log Send Queue counters to determine how synchronized the mirror database is with the principal database. You can also check the Log Bytes Sent/sec counter to monitor the amount of logs sent per second.
For a complete list of performance counters, please refer to:
Https://msdn.microsoft.com/zh-cn/library/ms189931.aspx
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.