Activity overview
Latest activity by daniel.rothig
Hi all,
Sorry to everyone who's experiencing this. Just to confirm, we are currently looking into this performance regression - all signs point towards an issue with caching in SQL Monitor 5.0.2, so rolling back to v5.0.1 or v5.0.0 will likely improve things. We hope to have a fix for you early next week.
Thanks
Daniel Rothig
Product Manager for SQL Monitor
Redgate / comments
Hi all,
Sorry to everyone who's experiencing this. Just to confirm, we are currently looking into this performance regression - all signs point towards an issue with caching in SQL Monitor 5.0.2, s...
SQL Monitor 5 - beta one
Welcome to the SQL Monitor 5 forums!
The latest beta for SQL Monitor 5 is now available. It features Active Directory integration, meaning that you can now share access to SQL Monitor without havin...
You could, however, configure a maintenance window for the server in question (go to Configure -> Monitored servers -> right-click on the server -> Set Maintenance Window). This will disable alerts for that server for a time pattern you can specify.
Hope that helps
Daniel Rothig
Product Manager
Redgate / comments
You could, however, configure a maintenance window for the server in question (go to Configure -> Monitored servers -> right-click on the server -> Set Maintenance Window). This will disable alerts...
SQL Monitor v3.10 has been released
Hi all,
We have released SQL Monitor 3.10 today. If you are a user of SQL Monitor v2 or SQL Monitor v3, you are entitled to upgrade.
This release addresses a security vulnerability identified in SQ...
SQL Monitor v4.2 has been released
Hi all,
We have released SQL Monitor v4.2 today. This release addresses a security vulnerability identified in SQL Monitor.
For more information and links to the download, see http://www.red-gate.c...
As suspected, we use "Last batch time" to identify new queries, without checking if the plan handle has changed. So technically the alert is "long-running batch".
It's difficult to make everyone happy with these kinds of alerts, because the atomicity of operations is a business consideration invisible to a SQL Server specific monitoring product. Our assumption therefore is that batches are a unit of operation. Sorry if that doesn't work in your case. I'd recommend excluding the affected queries from the LRQ alert, and monitor the average duration of the sproc with a Custom Metric that queries dm_exec_query_stats.
Hope that helps
Daniel Rothig
Product Manager for SQL Monitor / comments
As suspected, we use "Last batch time" to identify new queries, without checking if the plan handle has changed. So technically the alert is "long-running batch".
It's difficult to make everyone ha...
Hi John,
SQL Monitor does use a fair number of transactions. We have found that a larger number of smaller transactions has a lower impact on the monitored systems, so that's the side we tend to err on when developing our monitoring routines. However, 5-6M transactions per day on the monitored system sounds extreme!! I believe something unusual was going on there. It might be worth opening a support ticket if you wish to drill into this.
Obviously, it's not possible to gauge load by any one metric (were it that simple!), but if you're particularly concerned with your transaction rate on TempDB, support can also help you to reduce the number of transactions SQL Monitor performs.
Hope that helps
Daniel Rothig
Product Manager for SQL Monitor / comments
Hi John,
SQL Monitor does use a fair number of transactions. We have found that a larger number of smaller transactions has a lower impact on the monitored systems, so that's the side we tend to er...
Hello all,
The SQL Monitor team are currently investigating this issue, and unfortunately we are not able to reproduce any of the reported blocks or deadlocks. The one reported case we have available is one of SQL Monitor deadlocking itself, and there is no data on SQL Monitor beginning to affect other Databases on the system, the way rcinator mentioned. If anybody else experiences these issues, any information you could provide on the following questions could be very helpful.
Have you noticed any instances of SQL Monitor deadlocking other, non-SQL Monitor queries on the server?
Do you also observe other deadlocks unrelated to SQL Monitor on the server? If other types of deadlocks abound on the SQL Server instance, it would point to a more general issue with the instance.
How frequent are these deadlocks? You've mentioned you are seeing multiple of them. / comments
Hello all,
The SQL Monitor team are currently investigating this issue, and unfortunately we are not able to reproduce any of the reported blocks or deadlocks. The one reported case we have availab...
Sorry we’ve been quiet for a while – 2014 was a very busy year at Redgate, as our roadmap shows. We’re are currently working on SQL Monitor, and hope to provide a roadmap update in a few months’ time, once we’ve got more certainty about our plans. / comments
Sorry we’ve been quiet for a while – 2014 was a very busy year at Redgate, as our roadmap shows. We’re are currently working on SQL Monitor, and hope to provide a roadmap update in a few mont...
Hi Richard,
We are currently researching ways to extend migrations to SSDT projects, allowing users to use this functionality without using Source Control, and I would be really interested learning more about your requirements for a solution. Do you think you would be available for a brief research call (ca. 30 minutes)? If you are, would you mind dropping me a line at daniel.rothig [at] red-gate.com for more details?
Many thanks
Daniel Rothig
Product Manager
Red Gate Software / comments
Hi Richard,
We are currently researching ways to extend migrations to SSDT projects, allowing users to use this functionality without using Source Control, and I would be really interested learning...