The danger of over monitoring SQL Database with Solarwinds product?

Can monitoring the busy SQL Server production workloads with multiple SolarWinds products lead to harm or even database corruption, resulting in downtime or at least performance effects?

I have these products available under my current licensing scheme and would like to know if combining these products to monitor the SQL Server database is or can be dangerous or not.

Any help would be greatly appreciated.

Find more posts tagged with

sql

sqlserver

Database

Accepted answers

All comments

jm_sysadmin

Generally anything you do adds work, but Monitoring is not a heavy load. Most SQL servers won't notice the work, but you should be careful as you add it on and pay attention, maybe add development or test servers first.

Seashore

I agree with @jm_sysadmin . In my experiance, DPA and AppInisght for SQL are well tuned not to impact the SQL very much. But with your own custom SAM templates, it's up to you to know what you are doing. Just as bad user queries can heavily impact SQL, so can your queries that you let SAM run on SQL.

Database corruption, no you will not damage your databases by monitoring them.