Skip to content

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.


In Redgate Monitor, I want to...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • or

756 results found

  1. Add 2017 CU14 to Estate view

    Currently SQL Monitor shows the latest SQL Server 2017 version to be CU13 yet the latest is CU14. This should show the latest version.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  2. Extend field width of Server Selector field on top of Dashboard to be the same width as the Drop Down

    Go to Dashboard; Overview tab; drill down to one of the servers. On top of this next form (Server Host Metrics form) is the Server Selector field with a Drop Down list box. When you select the down arrow key to open the List Box the width of the List box is about twice the width of the Server Selector field. Is it possible to make the width of the Selector field the same as the drop down or make it user defined/variable? Right now it's around 27 chars. We have long server aliases/names so if extended, it…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Pie chart in SQL versions estate page to have CU patch status rather than SQL server version

    Pie chart in SQL versions estate page to have CU patch status rather than SQL server version

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Job step failure - trigger an alert, even if the job itself doesn't fail

    CONTEXT: If job step "On failure action" is set to "Go to next step" or "Go to step xy...." and the step fails, we would like to be alerted. The alert should be triggered immediately (as opposed to at the end of the job).

    PROBLEM: SQL Monitor "Job failed" alert doesn't alert in such cases.

    EXAMPLE SOLUTIONS:
    • A new alert.
    • Expanding options on the "Job failed" alert.

    53 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →
    completed  ·  Carlos Eriksson responded

    As of version 13.0.55 (February 27, 2024).

    Job failing alerts can now be raised when any individual job step fails, even if the overall job succeeds.

  5. "Installed Versions" tab needs to be aware of GDR updates

    Only Service Packs and Cumulative Updates are currently included in the version list maintained by Redgate, which drives the "Installed Versions" tab. GDR updates are not included.

    In my estate, this has resulted in SQL Server 2012 SP4 installations showing as being fully up to date, when there is a GDR update from January available, to address Meltdown/Spectre.

    Microsoft's official line on GDR updates for SQL Server is:

    "A GDR addresses an issue that has a broad customer impact, that has security implications, or that has both. A GDR is determined and issued by Microsoft as appropriate and when appropriate.…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  6. We would like to send slack messages to different channels depending on the server.

    We have multiple teams who are ultimately interested in what is wrong with their platform, The posting to a single slack channel is good, however giving an option to send only messages from certain servers to specific channels would improve our customer engagement. currently the main channel is ignored by the all teams except the dba's as the chaff from other servers can cause disinterest, or interest when no reason for a team to investigate.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. Use extended events for deadlock "tracing" instead of a trace flag

    If the SQL Server version is high enough, using extended events to capture deadlock information would be preferred to using a trace flag.

    138 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    22 comments  ·  Admin →

  8. Suspend Monitoring of Individual Cluster Nodes

    Alert suppression windows can be applied to groups, clusters, instances, and machines - including individual cluster nodes. Howerer it seems it is only possible to suspend monitoring for instnaces or clusters not individual nodes,

    We recently had a hardware fault and it would have been helpful to suspned monitoring of a specific node whislt the engineer resolved the fault.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. Show current data sizes on purging page

    On the data purging page would it be possible to show for each of the data categories how much space each one is currently occupying.

    Possibly even an 'oldest date' too? As this may be pertinent if the purge thresholds haven't yet been met.

    On some environments I want to keep as much SQL Monitor data as possible and if it's a healthy server you may have very little alert data, and so want to keep more history than you do say, machine data.

    It would also help in cases where the Repository database is growing, and you're not sure…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. Add scheduling for monitoring suspension and resumption

    Using Azure SQL Database in serverless mode with an auto-pause is a useful feature to save money when the db is not in use. SQL Monitor keeps the db from sleeping overnight.

    Suggest addition of scheduling for Suspend/Resume operations, similar to alert suppression scheduling.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  11. Set Maintenance Window by Group

    We do maintenance by class of server (DEV, QA PRD) and update an entire group during one maintenance window. It would be nice to be able to select a group like "Production" and set one maintenance window instead of setting it for each server. And since we do maintenance on the second Sunday for one group and the third Sunday for another we can't set a window and forget it. We have to set it before the weekend there will be work done and then clear it on the following Monday. More scheduling flexibility would be a wonderful addition.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Apply filters to more SQL Server alerts

    In configuring Long Running Query, I'm able to specify a filter on the process name (e.g. wanted to exclude my "Barracuda" backup processes - and did so successfully). I'd like to do the same for other Alerts such as Deadlocks and Blocking Processes.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. Backup overdue alert - RegEx filter

    I have many non-production databases on production SQL Instance, that make no sense to backup. I know I can turn this alert off one by one on each database. RegEx filter by database name would be help.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. Cluster Roles that have been renamed should no longer have an entry with the old name

    Over the last year and a half I have migrated several SQL FCI's to new windows clusters, new hardware, windows and SQL versions. To accomplish this with minimal downtime I had to setup the cluster roles ahead of time with everything ready to go prior to doing a final tlog backup/restore and rename of the cluster instances. This has worked well for us however SQL Monitor creates a new server record when the instance is renamed and never gets rid of the original name of the the new instance. This has left me with SQL Monitor still showing this nonexistent…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  15. network adapter name on overview page

    Currently network adapters' interface description is shown on the overview page of a monitored server. i am not interested of that information really, I would see the net adapter name as Get-NetAdapter cmdlet returns. So, Name should be there instead of the description.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  16. With the AG Groups it would be good to have soft alerting on configurations

    With the AG it is possible to have different configuration on the server replicas. We mostly get caught out with Logins. but have had issues with XMLBlob size, linked servers and Server Master Keys.

    It would be good for monitor to alert (or be able to alert) if a Login does not exist on both (all) replicas. we have times when a quick addition through SSMS does not put the same login on all side. when fail over occurs we then have broken processing. It would be good for sids to be checked as well as this is another…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  17. Simpler Upgrade \ Patch Process

    The upgrade process is a bit long winded. It would be great if the system could be upgraded or patch with a single click. Ideally within SQL Monitor but if not, downloading the file and just selecting upgrade would be great.

    86 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Daniel Rothig responded

    Thanks Phil – we are considering reworking the upgrade process. If this suggestions gains more traction, we’ll prioritise it higher

  18. Grant access to the Security Auditing features to a specific user role or user group

    As a DBA, I wish to grant access to the Security Auditing features (Permissions changes and Configuration compliance) to our security team. I do not wish the security team to have full administrator access to the Redgate Monitor installation as they are not DBAs and neither interested in nor responsible for any other parts in Redgate Monitor.

    At the moment, only Redgate Monitor administrators have access to the above enterprise security features in Redgate Monitor. From a separation-of-duty perspective, the security team should not have full access as administrators to the Redgate Monitor installation.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  19. Alerts should configurable to repeat until an issue is resolved

    We'd like the option for alerts to repeat until an issue is resolved. For instance, we may have a custom alert to tell us when a DBCC CheckDB hasn't been performed in >24hrs. For that we'd perform the check once per day and expect to get an alert every day that the problem continues. Without the alert recurring it's very easy for it to slip through the cracks and get missed.

    Another example is blocking. We have some databases where we monitor blocking via SQL Agent and when a block occurrs for 1m or more, we send emails every 30s…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  20. Identifiy the failed job steps when a job has failed

    CONTEXT: When looking at a job failed alert, we would like to pinpoint why it has failed.

    PROBLEM: SQL Monitor doesn't indentify the failed steps - we have to go to SSIS to get that information.

    EXAMPLE SOLUTIONS:
    • Add this information to the "Job failed" alert
    • Provide a query to make retrieving this data more convenient

    136 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    11 comments  ·  Admin →
    completed  ·  Adam responded

    Thanks for this suggestion. Failed job steps are now listed in failed job alerts – this feature was completed in Version 7.1.6, released October 4th 2017 (apologies for not updating sooner).

    We have marked this as completed – please let us know if you believe this needs to be reopened, or add a new suggestion if you would like to see a particular improvement.

    Thanks,
    SQL Monitor Development Team

1 2 … 14 16 18 … 37 38
  • Don't see your idea?

Suggestions

Categories