756 results found

1. Password is blank when accessing the edit credentials in Monitored servers

   Password is blank when accessing the edit credentials in Monitored servers for the monitored sql instance .
   If any options need to be changed will need to update the password for the SQL and OS credentials

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   declined  ·  Neil Turner responded

   The password is intentionally blank. This is to prevent users that don’t have access to the server from changing these settings.

2. Customize Estate Version Thresholds

   On the estate tab, it would be nice to customize the thresholds that define the yellow and red state. For example, a server behind on one CU might be yellow, but others red.

   5 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Add more narrow time intervals in Reports

   We are using the reports part of SQL Monitor to show them on a TV screen in a proactive way and we find this very helpful.

   Now we have a question, would it be possible to include more narrow intervals like 6 h, 2 h and 30 min in the reports?
   Because even if we lower the reports to 12 h and has auto refresh every 1 min it’s kind of hard to see and react on the spikes in the graphs.
   An example can be seen in the attached fil - Batch request/sec report, it’s hard to spot the spikes.

   I know that the purpose of reports might not be the way we use them. But we found them very helpful and by using them in this approach we don’t need any other tool for this “proactive TV monitoring”.

   Thanks!
   /Ted

   We are using the reports part of SQL Monitor to show them on a TV screen in a proactive way and we find this very helpful.

   Now we have a question, would it be possible to include more narrow intervals like 6 h, 2 h and 30 min in the reports?
   Because even if we lower the reports to 12 h and has auto refresh every 1 min it’s kind of hard to see and react on the spikes in the graphs.
   An example can be seen in the attached fil - Batch request/sec report, it’s hard to spot the… more

   •  

   12 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   completed  ·  Adam responded

   Thanks for this suggestion.

   Version 9.0.8 has been released which has added 30 minutes, 1 hour, 2 hours and 6 hours to the Reports time filter values
   https://documentation.red-gate.com/sm9/release-notes-and-other-versions/sql-monitor-9-0-release-notes

   We’ll mark this as completed and welcome any further feedback you might have.

   Thanks,
   SQL Monitor Development Team

4. domain

   Have the Redgate Monitor application support multiple AD domains for users. I have over 4 domains with users that want access to the application.

   3 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Custom disk alerts in a cluster is lost when instance is moved to a new host

   We often use customized disk alerts for larger disks i.e. instead of using the default alerts we might configure a High alert at 200 GB and a medium at 250 GB.

   These custom alerts is not set on the instance level so when we move the instance to a new host the custom alerts will not follow the instance and the alert has to be set up again.

   As our largest cluster is 9 node cluster with 23 instances and 3 disk each this cause us to configure these alerts at a maximum of 621 instead of 69 times. That is a huge difference.

   Would it be possible to tell SQL Monitor that a specific alert is an “Instance configure alert” instead of a Host alert and that it should overrides the Host alerts? Alternatively, some other solution.

   Thanks! /Ted

   We often use customized disk alerts for larger disks i.e. instead of using the default alerts we might configure a High alert at 200 GB and a medium at 250 GB.

   These custom alerts is not set on the instance level so when we move the instance to a new host the custom alerts will not follow the instance and the alert has to be set up again.

   As our largest cluster is 9 node cluster with 23 instances and 3 disk each this cause us to configure these alerts at a maximum of 621 instead of 69 times. That… more

   21 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Skip warnings on Database Snapshot Backups

   I'm seeing warnings about backups not getting done on snapshots. Obviously it's not looking at the type.

   16 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   completed  ·  Daniel Rothig responded

   Fixed in SQL Monitor 5.0.2

7. Configurable Thresholds Based on Time

   The alerts would be more useful if we could apply maintenance or quiet periods to them.

   I understand we have the maintenance window and that is perfect for things like planned downtime, index maintenance etc.

   Regards,
   Clive

   However, the issue I currently face is that I suppress the processor under utilised message. Like a prolonged spike in CPU activity, a massive drop off could be a concern too. However, I have a current mean of 18.6% on one example server. I can set a threshold of 15% as an example, but this would trigger alerts through the night when typically from 1am to 6am there is no load on the server. using the "For longer than ... seconds" box is not really useful if I am checking the CPU over a 6 hour period as I could miss issues during the business day.

   In my mind, it would be great if I could set the alert to trigger when we are below 15% but only during X and Y time.

   The alerts would be more useful if we could apply maintenance or quiet periods to them.

   I understand we have the maintenance window and that is perfect for things like planned downtime, index maintenance etc.

   Regards,
   Clive

   However, the issue I currently face is that I suppress the processor under utilised message. Like a prolonged spike in CPU activity, a massive drop off could be a concern too. However, I have a current mean of 18.6% on one example server. I can set a threshold of 15% as an example, but this would trigger alerts through the night when… more

   8 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Link to alert within Teams notification

   I would like to see a direct link to redgate monitor alert within the teams notification. At the moment I have to search for the alert in the WebUI manually instead of clicking a direct link like it is in a mail notification with "View full alert details" button.

   •  

   5 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Retain user last selection and update current default time options to be more flexible

   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… more

   •  

   6 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Remove "Configure alert" link from alert emails

    This is a big issue for me because I send Job Failure alert emails to the development team, but I don't want different people configuring alerts on Redgate Monitor. Only DBA's can make changes to the monitoring configuration.

    I don't think the "View full alert details" is necessary either. If developers need to see more information, they can look at the Job History.

    4 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Webhook Filter on Alert Severtiy

    Situation: After setting up a webhook of SQL Monitor to Service Now we are getting tickets of all priorities

    Background: We would only like tickets to be created that are actionable

    Assessment: We can enable this on the javascript side of the service now webhook to remove low priority webhook calls however it would be prefered to do it in RedGate

    Recommendation: Is it possible to have the same feature that email has "Call webhooks only if alert severity is High or Medium only"

    9 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    completed  ·  Liam Prescott responded

    Support for configuring the alert level at which Webhook notifications are sent was added in version 13.0.52.

    In Configuration > Notification settings you can configure Webhook notifications to be sent for all levels of alerts, all high and medium alerts, or just high level alerts.

12. Receive an alert for the process that is blocking not the process being blocked.

    We recently upgraded our SQL Monitor to version 5.1 and it appears there has been a change in the Blocking process metric. Before the upgrade we received an alert about a process that was blocking and after the upgrade it appears we receive an alert for each of the processes being blocked. We have set the threshold for 90 seconds and if there are three processes that are 30 seconds that total the 90 seconds, we receive an alert. However we don’t want to receive an alert for the 30 second blocked processes. Is there a way we can understand this change or configure it so we don’t get alerts that are blocked for less than 90 seconds?

    We recently upgraded our SQL Monitor to version 5.1 and it appears there has been a change in the Blocking process metric. Before the upgrade we received an alert about a process that was blocking and after the upgrade it appears we receive an alert for each of the processes being blocked. We have set the threshold for 90 seconds and if there are three processes that are 30 seconds that total the 90 seconds, we receive an alert. However we don’t want to receive an alert for the 30 second blocked processes. Is there a way we can understand… more

    10 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  Neil Turner responded

    See https://documentation.red-gate.com/sm/metrics-alerts-and-notifications/metrics-and-alerts-reference/list-of-alerts#Listofalerts-BlockingProcess

13. Configurable Alert Thresholds for notification alerts

    I would like to suggest a new alerting feature for Redgate Monitor: the ability to configure notification thresholds based on the number of consecutive occurrences of an event.

    For example, for SQL Server Agent Job failures, it would be useful to define a threshold so that an alert is triggered only after a job has failed a specified number of consecutive times (e.g., 3 or 5 failures), rather than generating a notification for every individual failure.

    This enhancement could help reduce alert fatigue and notification noise, especially in environments where occasional transient failures may occur and do not require immediate attention. By allowing users to focus on recurring or persistent issues, alerting would become more meaningful and actionable.

    Ideally, this capability could be available for SQL Agent Job failure alerts and potentially extended to other alert types where repeated occurrences are more significant than isolated events.

    Thank you for considering this suggestion.

    I would like to suggest a new alerting feature for Redgate Monitor: the ability to configure notification thresholds based on the number of consecutive occurrences of an event.

    For example, for SQL Server Agent Job failures, it would be useful to define a threshold so that an alert is triggered only after a job has failed a specified number of consecutive times (e.g., 3 or 5 failures), rather than generating a notification for every individual failure.

    This enhancement could help reduce alert fatigue and notification noise, especially in environments where occasional transient failures may occur and do not require… more

    4 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Alert for full filegroup

    if a database is a fixed size (max size set), or if the db is initially set to be the full size of a disk, there is no alert to let us know that the database is full.

    for instance - if T: drive contains tempdb (and only tempdb) and we've sized it to take the whole drive. we've done funky sizing and growth settings so we can get an alert when the db grows, but once its grown and the temp objects are cleared, we're unlikely to get another disk warning, because the DB will already be taking 100% of the disk.

    If we could get an alert on the error below - it would allow a greater degree of flexibility when databases fill up (due to fixed size or expired disk space alerts)

    Could not allocate space for object 'dbo.#wak' in database 'tempdb' because the 'PRIMARY' filegroup is full

    if a database is a fixed size (max size set), or if the db is initially set to be the full size of a disk, there is no alert to let us know that the database is full.

    for instance - if T: drive contains tempdb (and only tempdb) and we've sized it to take the whole drive. we've done funky sizing and growth settings so we can get an alert when the db grows, but once its grown and the temp objects are cleared, we're unlikely to get another disk warning, because the DB will already be taking 100%… more

    6 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Make the alerting system AG Aware

    Similar in nature to the Job Duration Unusual Alert should be AG aware - there are many alerts we do not want to see on an AG secondary unless it is set to readable - things like server waits due to queries running on master etc generate alerts when running against a base line but we dont need to get the alert/notification if the AG is set to secondary

    9 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Only Alert Database File Usage on one copy of a database in Availability Group

    When monitoring all instances of an Availability Group, the Database File Usage alerts on every instance. This just adds extra noise. It would be great if instead of alerting on each copy it just alerted once on the availability group somehow.

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Globally enable/disable monitoring

    We would like the ability to quickly turn off and on all monitoring and alerting globally. This would be usefull when we have major outage that we become aware of and start to work on, however alerts get generated very quickly and can overwhelm the email system or support phone. It would be great if we could continue to collect performance metrics but stop all alerts until the problem is resolved.

    6 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  Daniel Rothig responded

    Go to Manage Monitored Servers, Select All, Suspend.

18. SQL USER PROCESSES (TOP 10 BY CPU) - drill down

    Server hosts/matrix
    Drill down
    Some select's come up in mine, but I'm not able to drill down to find more details like the SQL itself

    4 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Want Estate page to report patch correctly for GDR only instances.

    In the SQL Server versions page under Estate, Redgate Monitor checks for the “Latest available update” for each SQL instance. It compares the instance level with the latest patch released on the CU-path for the instance version and sets the Status column as appropriate, flagging where a patch is missing, be that CU or CU+GDR.

    I would like an option to set specific SQL instances to be on the GDR-only pathway and have Redgate Monitor check and provide accurate last GDR patch and status detail for those too.

    Without this change, GDR-path instances can show as "update needed" (yellow) in the Status column when they are already on the latest GDR patch and manual checking is required to confirm that they are indeed up-to-date.

    In the SQL Server versions page under Estate, Redgate Monitor checks for the “Latest available update” for each SQL instance. It compares the instance level with the latest patch released on the CU-path for the instance version and sets the Status column as appropriate, flagging where a patch is missing, be that CU or CU+GDR.

    I would like an option to set specific SQL instances to be on the GDR-only pathway and have Redgate Monitor check and provide accurate last GDR patch and status detail for those too.

    Without this change, GDR-path instances can show as "update needed" (yellow) in… more

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. SQL Versions Page

    Hi there,

    We maintain a number of legacy SQL Servers that are still monitored via SQL Monitor. I regularly use the SQL Versions page to identify which instances require patching.

    However, some of these servers are under a permanent patch freeze, and I’d like to update their status to “OK” so they no longer appear as needing attention.

    It would be amazing if one could update the patch status for these servers within Redgate to mark them as compliant to reflect their frozen state.

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating