SQL Server Performance when monitoring a large number of databases using SQL Monitor
TerryG
Posts: 3 New member
We have two SQL Servers with a large number of databases. The servers are in AWS EC2.
One server has around 750 databases and CPU load spikes to around 80% multiple times during business hours. Some of the databases have a small number of connections (less than 10 users) and some databases have a large number of connections (around 100 users).
The other server has around 350 databases and the CPU load is around 40%.
How much additional load to the CPU should I expect to see when implementing SQL Monitor for these two servers? My concern is especially with the server with the larger number of databases as we have to make sure that we don't max out the CPU on that server.
One server has around 750 databases and CPU load spikes to around 80% multiple times during business hours. Some of the databases have a small number of connections (less than 10 users) and some databases have a large number of connections (around 100 users).
The other server has around 350 databases and the CPU load is around 40%.
How much additional load to the CPU should I expect to see when implementing SQL Monitor for these two servers? My concern is especially with the server with the larger number of databases as we have to make sure that we don't max out the CPU on that server.
Tagged:
Best Answer
-
lgivens
Posts: 5 New member
Hi Terry, I see you've already received a very good response. In addition, I would like to provide you some documentation that outlines details of recommended hardware and implementation considerations.
https://documentation.red-gate.com/sm/installing-and-setting-up/planning-the-sql-monitor-infrastructure-and-installation/hardware-and-performance-guidelines
Please let us know if you have any additional questions.
Answers
We have a small number of very large and extremely active databases - we noticed no increased activity when we first insalled Redgate Monitor.
However, if you're thinking of installing SQL Monitor onto the same SQL server that you want to monitor, don't. Ideally, SQL Monitor should be on it's own server. If you install it onto the same server that you are monitoring, if that server has issues, SQL Monitor might not be accessible and might not be able to record any activity.
Thanks for your reply. That's good to hear that you didn't see any increased activity once you started using SQL Monitor.
We intend to install the application on a different server than the SQL servers we are going to monitor.
Can anyone else in the forum share their experience with server performance after installing SQL Monitor?
Thanks for your reply. That's good to hear that you didn't see any increased activity once you started using SQL Monitor.
We intend to install the application on a different server than the SQL servers we are going to monitor.
Can anyone else in the forum share their experience with server performance after installing SQL Monitor?