Suggestions
Welcome to the Redgate Monitor feature suggestions list. Tell us how we can improve Redgate Monitor by voting on these suggestions or by submitting your own ideas.
This is the easiest way to make an impact on Redgate 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.
To give your idea the greatest possible impact, please follow these guidelines:
- Describe the goal you’re trying to accomplish, rather than a specific solution to get there
- If you have a favoured solution, add it as a comment to your suggestion
- Give us as much context as possible
- Only make one suggestion per post. If you have multiple ideas, submit them in separate posts
- Comment and vote on existing posts to develop the ideas — the Redgate Monitor team will often stay quiet initially about new suggestions to see what you have to say!
If you have any questions visit the Redgate Monitor forum.
- or
733 results found
-
Make software FIPS 140-2 compliant
Currently SQL Monitor is not FIPS 140-2 compliant
5 votes -
Enter and assign purchased SQL licenses to VM hosts, VM or server
The new SQL licensing tab would even make it possible to detect unlicensed instances depending on listed availability or improper VM host movement rules.
6 votes -
Block Specific Deadlocks by Lock Details
We've just updated to SQL Monitor 6. We was hoping there was a feature in this to change alert settings for Deadlocks with specific lock details rather than just all Deadklocks.
For example
we don't want email alerts on: Deadlock 'object: ReportServerTempDB.dbo.SessionLock, lock mode: Exclusive (X), index: IDX_SessionLockHowever we wish to receive emails when: Deadlock 'dbid: 6, object id: 72057594038845440, index id: (9bf78693a4b4)'
However this feature doesn't exist. Would be great to have added to an update in the near future!
42 votesThanks for this suggestion and the comments.
As previously announced, since version 8.0.22 (released November 13th, 2018) Deadlock (XE) alerts can now be filtered by database, login name & resource, and victimless (eg Exchange Event) deadlocks are excluded by default.
We are marking this as complete, but please do let us know if you have any further feedback.
Thanks,
SQL Monitor Development Team -
Use extended events instead of trace when trace initialized due to alert
I have seen a related idea https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/5717202-use-extended-events-for-deadlock-tracing-instead
However, I'm expanding this. If the SQL version is high enough the trace of current activity should be using extended events instead of a trace, this would reduce the total impact to the server performance while also expanding the available information.
98 votes
Daniel Rothig
responded
Thanks for the suggestion – we’ll monitor how popular it gets
-
Integrate with Policy Based Management
It would be really good to integrate with Policy Based Management to raise status alerts in SQL Monitor, that way we could breakout more complex Instance status
9 votes -
Group instances, not servers
For example: when I have a database cluster running multiple instances I would want have the possibility to put one instance in a development group and another instance from that same cluster in a different group. In this way managing alert settings etc on a group level becomes much more convenient.
37 votes -
Add the ability to create new alerts
Instead of limiting the available alerts to a pre-defined list, allow users to create new alerts and threshold metrics based on customized queries. In my opinion, this is about the only glaring omission in the current version of sql Monitor.
13 votesIncluded in SQL Monitor v3.0
-
know who ran SQL Compare and what changed
within SQL Monitor when it flags that SQL Compare ran, it would be good to be able to see who ran the job and what was changed. Currently the job is flagged in SQL Monitor but there seems to be no further details other than what database it ran on.
3 votes -
Testing the Availability Group listener(s)
If an Availability Group listener is not working for any reason (like no DNS resolution), but the ressource is still up in the cluster, SQL Monitor will not raise any alert.
Could you add a specific test for SQL monitor to test the connection using the availability group listener(s) and raise an alert if not successful?
7 votes -
Add custom metrics to Overview(s)
Add the ability to choose what is displayed on the overview for a given server/instance - especially with the addition of custom metrics.
Even better would be to allow the addition of multiple overviews (aka Dashboards) and configure what each one displays.
25 votes
Daniel Rothig
responded
We like that idea – if it gains traction, we’ll prioritise it more
-
Trend Analysis and Forecasting for Azure SQL Database capacity
A previous feature suggestion, https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/11122308-forecast-and-plan-disk-database-capacity, was completed in 2018. However, it does not include storage for Azure SQL Databases or Elastic Pools. While we can alert on this, we get no trend analysis or forecasting.
Selecting All Disks and All Groups on the Estate | Disk usage page gets us "No disks match your filter criteria."
2 votes -
Utilize SQL (or SQL-like) statements in filters.
Utilize SQL (or SQL-like) statements in the filters, specifically on the Overview tab to filter on server name. For example: '%sql%' AND '%prod%'
Currently you can only do 1 fuzzy logic search. Also, you cannot search just by one character.24 votes -
Show the database name not just dbid in the Lock Details of a Deadlock alert
I've got to do the extra step of:
SELECT name,dbid
FROM master..sysdatabasesto figure out which database the deadlock is referring to... shouldn't have to do this.
71 votesDatabase name is now shown for 2005+ deadlock alerts following the v4 release.
Thanks again for the suggestion and votes.
-
Add User Settings feature
Add a User Settings feature that will hold all user preferences, as different DBAs / users have different ways in using SQL Monitor. For example - (1) ability to display on the Overviews page only desired health levels (Critical, Warning, etc), or named group, or base monitor, or any combination, rather than load all servers from all groups from all base monitors. I really don't want to know that I have 265 healthy out of 275 servers - this will speed up loading of the Overviews page. (2) any other user preference.
4 votes -
be able to extract all alerts at once rather than extracting for individual alerts via API
Redgate Monitor API currently allows users to extract alert details for individual alert types. We need an API endpoint that can extract alert details for all alert types instead of calling the API multiple times.
10 votes -
Don't check Agent status for Express Edition
Whenever I add a server to the monitoring that is Express Edition, I get alerted that the SQL Agent service is not running.
Well d'uh. It's Express Edition. The Agent service cannot run on it.Instead of always giving me this alert and then having me go in and disable it for yet another server, why not change the logic to not raise this alert at all when the edition is detected as Express?
3 votesThis was fixed in version 9.0.10 released on May 1st https://documentation.red-gate.com/sm9/release-notes-and-other-versions/sql-monitor-9-0-release-notes
Please update to the latest version and let us know if that does not solve the issue for you.
Thanks
SQL Monitor Team -
Filter Longest Running Queries Tile by Database
The Longest Running Queries Tile on the Reports screen would be more useful if we could target only one database.
20 votes -
date format
I'd like to have an ability to set date format according to the country where the monitored SQL server is in, e.g. USA where date format is MM/dd/yyyy vs UK as dd/MM/yyyy. Also, why not to read and set date format off of the monitored server? Please make it configurable and country compliant so to speak..
Thanks,
Yuriy4 votes -
Should have feedback on missing index, its great know that I have a slow running query but some possible hints on how to improve them.
Should have feedback on missing index, its great know that I have a slow running query but some possible hints on how to improve them,
the infomation is avalible in SQLServer version 2005 onward in the following DMV
sys.dmdbmissingindexdetails
sys.dmdbmissingindexgroupstats
sys.dmdbmissingindexgroups
sys.dmdbmissingindex_columnsSo I still have to go off and check.
Overtime as database grow in size and data distribution of the tables changes therefore indexing requirements change, so unless you monitor these DMV's you may not notice that an index may be…34 votesThe missing indexes DMVs are not an exact science, so we’ve decided against presenting sometimes-helpful, sometimes-disasterous tuning advice in SQL Monitor.
However I’m confident that SQL Server itself will continue to evolve as a tuning platform, leaving SQL Monitor free to look at the bigger picture.
-
Preserve license after the upgrade
During an in-place upgrade of Redgate Monitor, the license is lost. This poses a significant challenge for offline environments where internet access is restricted. As a result, Redgate Monitor ceases monitoring after the upgrade until a new permit file is generated and uploaded, leading to gaps in monitoring history.
This issue could be mitigated if Redgate allowed a short grace period of trial or honored the previous license during the transition.6 votes
- Don't see your idea?