Post reply

SQL Server Monitoring - Is it reasonable to use the monitored SQL Servers resources such as tempdb?

  • July 18, 2016 at 12:07 pm

    #400425

    I recently ran into a potential issue with a SQL Server monitoring application and I'm wondering if I am being unreasonable in my expectations for the product with regards to the impact it has on the performance of the SQL Server(s) its monitoring. Presumably threes no way to monitor SQL Server without leaving some level of a footprint so the question in my mind is what is a reasonable level of impact?

    For example is it reasonable for the monitoring software to use the resources on the SQL Server(s) its monitoring such as tempdb? I would think that the software would avoid using tempdb on the SQL Instances its monitoring and if necessary use the tempdb located on the SQL Server where the apps own data store is located, the place where it keeps the information it captures. However I may be unreasonable in this assumption and so I would like to know what others think about this?

    I'm not mentioning the product by name because this is a general question for any SQL Server Monitoring solution. It may be that most do this and I am therefore being unreasonable to expect otherwise.

    Thanks

    Kindest Regards,

    Just say No to Facebook!

  • July 18, 2016 at 2:31 pm

    #1890721

    It's reasonable in general. Whether that's reasonable for your situation is another issue.

    Every monitoring system has an impact. I'm not sure that anything up to 10% is a problem, if you know what the impact is and you have the overhead.

    As far as using tempdb, I think it depends. What does that do to your system? How much tempdb impact is from the app, how much from the monitoring system.

    Ultimately, I think you have to live with it, unless you have power to replace the system. Therefore, learn what the impact is.

    I hadn't thought about this before, but at Redgate, we make SQL Monitor, which has no agent on the instance. However, we do run queries, which could spill into tempdb. I doubt it's much, but not sure it's been measured.

    Disclosure: I work for Redgate Software.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply