716 results found

1. Select different purge data ranges depening of what group a server belongs to.

   We have different data retention requirements depending on what server is being monitored, but currently only 1 purge setting is available which covers all servers. An example of what I'd like to see would be to select to purge data older than 14 days for production/critical servers and a much shorter retention of data for test/development servers. This would be controlled by what group a server was a member of.

   30 votes

   Vote 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

2. Suppress Free Space monitor (Azure Hyperscale DB)

   When using Azure Hyperscale DB - the DB auto grows - therefore the Free Space monitor needs to be silenced/ignored forever (except if you about to hit the max of 100TB!)

   5 votes

   Vote 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. Pull Server Certification Info

   Would like to request enhancement to be able to create a report to pull Server Certificate info, and have an email sent out to notify us 30/60/90 days before hand when it will expire. Pull details like the certificate issuer, validity period, and common name from the server certificate installed on the target machine.

   4 votes

   Vote 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

4. Custom metrics in Analysis tab - allow grouping by metric type (machine / SQL Server instance / database)

   In Analysis tab in the metric choice window all custom metrics are currently grouped together and sorted alphabetically. I'd like to see them grouped by type similar to the out-of-the-box metrics (machine / SQL Server instance / database) - the type could be a new parameter for each custom metric, manually entered / changed.
   That would help when one has a lot of custom metrics.

   The result:
   - Machine metrics
   - SQL Server metrics
   - Database metrics
   - Custom machine metrics
   - Custom SQL Server metrics
   - Custom database metrics
   - (maybe also this: Custom uncategorized metrics)?

   3 votes

   Vote 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…)
   6 comments  ·  Delete…  ·  Admin →
   declined  ·  Daniel Rothig responded

   we have found that this is not how people use custom metrics in general, so adding this split by default would go against the practices of most of our users – the best workaround for those that do have this split is to add a prefix to their custom metric name – they are ordered alphabetically

5. Add COMPARE BASELINE option to the Reports in SQL Monitor

   In SQL Monitor 6.0.17.6667 the new Reporting feature is terrific, however I would like to see the addition to add the COMPARE BASELINE option to the Reports like Analysis option currently has. This would allow us to see if measurements like CPU, user connections etc are in line with a baseline of, say last week or way off.

   31 votes

   Vote 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

6. Add alerting for replication performance

   Include an alert to monitor replication performance. i.e based on the latency reading that you can view in Replication Monitor. The counters for this are "SQL Server Replication LogReader: Delivery Latency" and "SQL Server Replication Dist.: Delivery Latency". I'd like to be able to set the alert priority based on this.

   81 votes

   Vote 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…)
   4 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

7. In AzureSQL, I would like Redgate Monitor to not "keep awake" systems which are set to "sleep".

   Within AzureSQL you can set SQL Servers to be Serverless and also to "sleep after" a time window. This means you can save money for systems which are not heavily used.
   I think Redgate Monitor needs to have a "light touch" mode for such systems where it will firstly check the config and say "ok, this server is asleep, I dont need to look at it" before reporting maybe in the infomration status "system asleep". When the system wakes up, it should monitor as normal.
   This is a cost saving exercise since, after adding Redgate to our Legacy AzureSQL servers, the cost went up by £250 a month per system. (we've gone from £10 purely storage, to £250 because Redgate is keeping it awake. IF this were a higher spec system, this cost could have been more.

   Within AzureSQL you can set SQL Servers to be Serverless and also to "sleep after" a time window. This means you can save money for systems which are not heavily used.
   I think Redgate Monitor needs to have a "light touch" mode for such systems where it will firstly check the config and say "ok, this server is asleep, I dont need to look at it" before reporting maybe in the infomration status "system asleep". When the system wakes up, it should monitor as normal.
   This is a cost saving exercise since, after adding Redgate to our Legacy… more

   7 votes

   Vote 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. new altert for service state of PowerBI Reporting Services PBIRS like "SQL Server Reporting Service status (2017+)"

   In addition to SQL Server Reporting Services SSRS, we have more and more PowerBI Reporting Services PBIRS.
   For SSRS since 2017 there is a separate alarm "SQL Server Reporting Service status (2017+)" in Redgate.
   This tells us when an SSRS is no longer running. This also works.

   However, as far as I can tell, this alert does not cover PBIRS.
   Recently, customers increasingly want PBIRS instead of SSRS and unfortunately we do not currently see the status of the PBIRS service in Redgate and do not receive an alert if this service is not running.

   We know that PBIRS and SSRS are different products that are not an official part of SQL Server (anymore).
   SSRS and PBIRS are very similar from our administrator's point of view.
   However, SSRS and PBIRS are additional service extensions of the SQL server at this point, which we have to monitor in some way.

   It would be fantastic if Redgate could also display/report the status of PBIRS services.

   In addition to SQL Server Reporting Services SSRS, we have more and more PowerBI Reporting Services PBIRS.
   For SSRS since 2017 there is a separate alarm "SQL Server Reporting Service status (2017+)" in Redgate.
   This tells us when an SSRS is no longer running. This also works.

   However, as far as I can tell, this alert does not cover PBIRS.
   Recently, customers increasingly want PBIRS instead of SSRS and unfortunately we do not currently see the status of the PBIRS service in Redgate and do not receive an alert if this service is not running.

   We know that PBIRS and… more

   11 votes

   Vote 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. Activity monitor is showing "Blocked By" sessions that are not showing up in SQL Monitor

   Is there an issue with the blocking information in SQL Monitor or are there certain types of blocks that are excluded? We are seeing blocks displayed in the SSMS Activity Monitor that are not being displayed on the SQL Monitor Overview page for Blocked Processes.

   1 vote

   Vote 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. Server & instance stats on main window

    I'd like to be able to see at a glance the basic details of my instance and the server on which it is running.

    I would love if I could see the following on the main screen:
    • SQL Server Version — SQL Server 2022 CU16 | 16.0.4150 (CU16)
    • Server Version — WS 2022 21H2 | 20348.2762
    • Instance details — 3x 3.0GHz | 12GB | 1TB (or whatever is allocated to the instance)
    • Free Space — 0.1TB of 1TB (drives will have to be chosen)
    • Instance status — SERVER\NAMEDINSTANCE
    • No. of Instances — 6 (only needed if there are named instances)

    Obviously, there is too much info for one little box and a design screen would be needed per instance as well as a default.

    I'd like to be able to see at a glance the basic details of my instance and the server on which it is running.

    I would love if I could see the following on the main screen:
    • SQL Server Version — SQL Server 2022 CU16 | 16.0.4150 (CU16)
    • Server Version — WS 2022 21H2 | 20348.2762
    • Instance details — 3x 3.0GHz | 12GB | 1TB (or whatever is allocated to the instance)
    • Free Space — 0.1TB of 1TB (drives will have to be chosen)
    • Instance status — SERVER\NAMEDINSTANCE
    • No. of Instances — 6… more

    1 vote

    Vote 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

11. Uptime of my SQL server database servers

    I need to be able to account for yearly uptime for my SQL server estate and also receive proactive alerts when they are shutting down.

    1 vote

    Vote 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  ·  AdminLiam Prescott (Admin, Red Gate Software) responded

    An uptime summary tile, which shows all the servers in the estate sorted by uptime in ascending order, was added in version version 14.0.21 (August 20, 2024). 

    
    

    The "instance unreachable" will be fired when a monitored server shuts down.

12. Replace SERVER identifier with a hosts file friendly name

    As the ALIAS feature isn't working consistently across all pages and, in particular, email alerts, the means to replace the name of a monitored server is needed.

    E.g., if someone, not a DBA or person familiar with SQL Monitor, set up each server as an I.P. address, or an equally meaningless Rackspace device ID, it is unreasonable to assume that I.P. or RS device translation to named server, which in our case is a customer name+nature combo, is held in every recipient's brain, or that we should carry around a pocket-sized hosts file printout...

    If a simple operation such as swapping an I.P. for a friendly name were in place, it would obviate LOSING ALL HISTORIC DATA INCLUDING BASELINE INFORMATION for any such server. Loss happens simply because we must now ADD another server, configure all its exceptions to the default rules, kill all the "overdue" red-alerts, etc., etc., etc.. What a pain! Done it once, and do not look forward to 39 more...

    It seems that the "server identifier" should be decoupled by design from any machine identifier, thus, it would appear that a Swap Server Name and Host-Reference feature ought to be a quick fix. Hope the underlying data model supports that...

    This will save, literally, hours and hours of unnecessary reconfiguration and alert clearing effort per server.

    As mentioned above, preservation of baseline and historic data is of paramount importance, especially given the redesigned overview page and interactive charts - if we lose our history, the charts are rendered useless for quite some time.

    As the ALIAS feature isn't working consistently across all pages and, in particular, email alerts, the means to replace the name of a monitored server is needed.

    E.g., if someone, not a DBA or person familiar with SQL Monitor, set up each server as an I.P. address, or an equally meaningless Rackspace device ID, it is unreasonable to assume that I.P. or RS device translation to named server, which in our case is a customer name+nature combo, is held in every recipient's brain, or that we should carry around a pocket-sized hosts file printout...

    If a simple… more

    3 votes

    Vote 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

13. I want to be able to apply tags to SQL servers in SQL Monitor to better sort

    I want to be able to create more groups that a server is a member of. For example, I want to see all Production servers, or all servers associated with a specific team or department. I can group by only 1 item now. But, if I could tag servers, that would allow me to be more granular in my reporting.

    We do the same thing in VMware now. We can still use the same grouping structure that exists today, just create the ability to provide multiple tags to each server/instance.

    10 votes

    Vote 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…)
    completed  ·  1 comment  ·  Delete…  ·  Admin →

14. Make alert configuration levels more discoverable

    CONTEXT: In SQL Monitor, you can configure alert behaviour down to the object level (such as the Database or the Job level). This is useful e.g. when we have specific databases with different backup policies to our global configuration, since we can specifiy "special rules" for individual databases.

    PROBLEM: It is counterintuitive how to do so, and many people don't spot the left-hand drilldown navigation - this makes you think that you can only configure on the global and the server level! Also, when we have created an override, it's easy to forget so causes surprise when we change the global configuration and the "special" database's behabviour doesn't change.

    EXAMPLE SOLUTIONS:
    • Autoexpand the left-hand side navigation, draw attention to it
    • Add Disks, Jobs and Databases as child-elements to the left-hand navigation
    • show the configuration hierarchy when editing alert settings. Highlight levels where overrides exist. Allow to apply new configuration to multiple levels simultaneously

    What do you think about these solutions? Got another idea? Let us know in the comments!

    CONTEXT: In SQL Monitor, you can configure alert behaviour down to the object level (such as the Database or the Job level). This is useful e.g. when we have specific databases with different backup policies to our global configuration, since we can specifiy "special rules" for individual databases.

    PROBLEM: It is counterintuitive how to do so, and many people don't spot the left-hand drilldown navigation - this makes you think that you can only configure on the global and the server level! Also, when we have created an override, it's easy to forget so causes surprise when we… more

    178 votes

    Vote 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…)
    42 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
    under review  ·  Daniel Rothig responded

    currently under investigation

15. Prevent Active Directory lockout from a single failed attempt to log into the dashboard

    If the user mistypes their password when trying to log into the SQL Monitor dashboard, their Windows account gets locked out in Active Directory. This happens on the first failed attempt, so presumably there's an automatic retry happening.

    (This ticket is similar to https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/16845169-keep-from-locking-account-when-registering-server, but that one is for the server monitor login and this is for the dashboard user's personal login)

    7 votes

    Vote 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
    under review  ·  Neil Turner responded

    Hi,

    Thanks for flagging this. Can you please raise the issue with support so that we can investigate further? You can do so via by going to: https://productsupport.red-gate.com/hc/en-us

    Thanks,

    Neil Turner
    Design lead – SQL Monitor

16. See who is using SQL monitor

    Before I upgrade SQL Monitor I'd like to see who is logged in/using it so I can inform them.

    2 votes

    Vote 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

17. In the Estate view you are 2 CU's behind for SQL Server 2016.

    Currently SQL Monitor shows the latest SQL Server 2016 version to be SP2 CU4 yet the latest is SP2 CU6. This should show the latest version.

    1 vote

    Vote 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…)
    completed  ·  1 comment  ·  Delete…  ·  Admin →

18. Increase SQL Monitor email Alerts to larger than 400 KB

    We have some alerts for important servers that require you to login to SQL Monitor to see the full details because they exceed 400 KB. The alert currently reads:

    "Details
    Details omitted because they exceeded 400KB. Please log into SQL Monitor to view them.
    View full alert details
    Configure alert"

    Please increase this value so that we can see the full alert details within an email instead of having to login to SQL Monitor to see them.

    Thank-you!

    3 votes

    Vote 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

19. Print the server overview

    Print the server overview (scroll) to share with team members to assist in correction of failures.

    3 votes

    Vote 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. Licensing Clusters

    Since only one SQL server is active in an Active\Passive cluster, you should not require multiple Monitor licenses.

    50 votes

    Vote 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…)
    4 comments  ·  Delete…  ·  Admin →
    completed  ·  Daniel Rothig responded

    Currently, we are offering a 50% discount for passive cluster nodes. We’ll continue to review our pricing structure over time.

    Why do we charge money for passive nodes at all? Covering your passive nodes with monitoring is necessary to ensure that when a failover occurs, the passive node is in a healthy state, and the failover will be able to succeed. However, passive nodes don’t (usually) have complex performance characteristics, hence the discount.