Suggestions

Welcome to the Redgate SQL Monitor feature suggestions list. Tell us how we can improve SQL Monitor by voting on these suggestions or by submitting your own ideas.

This is the easiest way to make an impact on SQL Monitor’s roadmap. Check out the completed suggestions to see how your ideas have influenced us in the past. Please note that this list is one of multiple sources that drive our development, meaning that we will not always implement the highest-ranking suggestions.

We have a table in our administration database that contains usefull information for our management. This consists of multiple columns. It would be very helpfull to run a query in a tile in a report where the results of that query can be displayed. A bit like the long running query results in the reports but then with our own data from the administration database.

It makes no sense for there to be Alert configuration settings for tempdb for Consistency Checks, Backups, and any other irrelevance.

If the ONLY reason for the existence of SSRS databases is because of Microsoft's idiotic requirement for SSRS to actually be configured in 2014 before permitting an in-place upgrade to 2016, there is no ACTUAL reason why one would care two hoots about the state of either SSRS DB on ANY instance affected by this "demand". OK, I have just 21 instances to drill down to SHUT UP ABOUT SSRS DATABASES!

Please provide a better way to manage SYSTEM databases (I do not regard SSRS databases as "real" USER databases, despite SQL's classification as such). I need global settings that apply to standard SQL-named databases, not the current drill down every instance paradigm that is significantly man-effort-wasteful.

It makes no sense for there to be Alert configuration settings for tempdb for Consistency Checks, Backups, and any other irrelevance.

If the ONLY reason for the existence of SSRS databases is because of Microsoft's idiotic requirement for SSRS to actually be configured in 2014 before permitting an in-place upgrade to 2016, there is no ACTUAL reason why one would care two hoots about the state of either SSRS DB on ANY instance affected by this "demand". OK, I have just 21 instances to drill down to SHUT UP ABOUT SSRS DATABASES!

CONTEXT: We have some databases with multiple filegroups, I’d be useful to be able to drill down from the DB level to the FG level on the “Total data file size” and “Total data file used” metrics.

PROBLEM: Not being able to slice totals by FG is problematic, since different FGs often have different capacity / performance requirements, different space used speed/patterns etc.

EXAMPLE SOLUTION: For “Total data file size” and “Total data file used” add an additional selector window after the database selector: a list of filegroups + an (All) option at the top. So, the selectors would be: machine->instance->DB->FG

CONTEXT: We have some databases with multiple filegroups, I’d be useful to be able to drill down from the DB level to the FG level on the “Total data file size” and “Total data file used” metrics.

PROBLEM: Not being able to slice totals by FG is problematic, since different FGs often have different capacity / performance requirements, different space used speed/patterns etc.

EXAMPLE SOLUTION: For “Total data file size” and “Total data file used” add an additional selector window after the database selector: a list of filegroups + an (All) option at the top. So, the selectors would be:…

It would be great if you could have an override on each alert to allow for a customised email setting just for that alert.
Currently an alert can have a different email address BUT it only uses the default settings, if I wanted to fine tune for that alert I can't.
Thanks, Steve

On the Overviews of an instance Server/Host Metrics the default selections are always the last 24 hours as well as having all 4 boxes ( CPU, Memory, Disk I/o and Waits) select.

I am constantly having to uncheck the Memory box and most individuals look at the last 6 hours or would prefer ( 1 or 3 hours) and have to change from the default last 24 hours to last 6 hours each time navigating to this page. I would like to be able to have SQL Monitor remember my last setting(s) or at least be able to change the default for my user or all users.

Additionally it would be beneficial and practical to have a consistent UI time range across tabs. You can see across the three tabs (Overviews Analysis and Reports) the time range selection is different.

I would like to have all available time options of the 3 tabs combined and available. This would be the most beneficial to have a smaller time duration in the Overviews tab even going as far as having a Zoom range of 5 minutes compared to the current 15 minutes

On the Overviews of an instance Server/Host Metrics the default selections are always the last 24 hours as well as having all 4 boxes ( CPU, Memory, Disk I/o and Waits) select.

I am constantly having to uncheck the Memory box and most individuals look at the last 6 hours or would prefer ( 1 or 3 hours) and have to change from the default last 24 hours to last 6 hours each time navigating to this page. I would like to be able to have SQL Monitor remember my last setting(s) or at least be able to change the…

One of the most common alerts that we get is the Long Running Query alert. However, when the query is due to a package executing from an agent job, there is little to no information about what is running long. The attached image is an excerpt from one of the alerts we got this morning. We can tell it is from an executing job, because of the SSISDB database specified. But beyond that, we are left trying to figure out which job/package was the culprit by digging through execution logs and schedules, then trying to match execution lengths with where the alert would have been triggered. Maybe in a future release you can add which package is executing that triggered the alert.

One of the most common alerts that we get is the Long Running Query alert. However, when the query is due to a package executing from an agent job, there is little to no information about what is running long. The attached image is an excerpt from one of the alerts we got this morning. We can tell it is from an executing job, because of the SSISDB database specified. But beyond that, we are left trying to figure out which job/package was the culprit by digging through execution logs and schedules, then trying to match execution lengths with where…

When viewing an alert within the side-bar on the Overview page, clicking on the 'Go to the full details' arrow redirects the page to the intended alert. You have to then click back to see the overview page again.

It would be great for the ability to be able to open click through links on a new tab or window instead of the same window to prevent navigating away from the overview page.

Exclude all offline data bases from the overdue backup alert as we do not have a need to backup an offline data base. For us if a data base is taken offline it's most likely because its been migrated to another server or no longer needed and will eventually be deleted.

We would love to have Single Sign-On added so we can use CAS for authentication. This feature would really help make things easier even more so then LDAP/NTLM even... I know I been on a support ticket for weeks to have a "work around" be the answer.