Priya Sinha
My feedback
23 results found
-
1 vote
An error occurred while saving the comment -
121 votes
Good idea! If this suggestion gets more traction, we’ll implement this.
An error occurred while saving the comment
Priya Sinha
commented
Thanks for your suggestion Bill.
-
69 votes
Daniel Rothig
responded
We’re looking into this – no ETA at the moment
An error occurred while saving the comment
Priya Sinha
commented
Thanks for your suggestion Kevin.
-
180 votes
currently under investigation
An error occurred while saving the comment
Priya Sinha
commented
Thanks for your suggestion Niels.
An error occurred while saving the comment
Priya Sinha
commented
Thanks for your suggestion John and Jonathan.
Priya
An error occurred while saving the comment
Priya Sinha
commented
Thanks Don. We will definitely try to improve these alerts based on your feedback.
An error occurred while saving the comment
Priya Sinha
commented
Hi Don,
Thanks for your message. To supress an alert at database level, please follow these steps:
1. On the Configuration > Alert settings page, go to the left hand navigation.
2. Select and expand SQL Server instance.
3. You would see the list of the databases for this SQL Server instance. Select a database. This will filter the alerts on right hand side which are supported at the database level.
4. Now you can change configuration for this particular database.Please let me know if I am not clear.
Thanks,
PriyaAn error occurred while saving the comment
Priya Sinha
commented
Hi Don,
Thanks a lot for your suggestion. Currently we do support supressing alert for a particular database. You can do it by expanding under a particular alert on right hand side of Alert Settings. Though other ways of supressing alert is not supported. We will definitely try to improve in this area.
Thanks,
PriyaAn error occurred while saving the comment
Priya Sinha
commented
Hi Don .. Thanks a lot for your suggestion. We will review this based on your feedback.
Regards,
PriyaAn error occurred while saving the comment
Priya Sinha
commented
Hello ... thanks for your feedback. Could you please help us by explaining this in bit more detail.
An error occurred while saving the comment
Priya Sinha
commented
Thanks .. yes it makes sense. You mentioned maintenance window .. SQL Monitor does support maintenance window where you can stop alerting completely during maintenance . This can be done via Configuration > Monitored servers page.
But having said that, it does not support stopping a particular alert during maintenance window. So would be nice to know if the current implementation of maintenance window is enough or would be like this feature to be extended to support per alert maintenance window. Also, in what scenario would you like to be alerted about some alert in maintenance window and not about others.
An error occurred while saving the comment
Priya Sinha
commented
Thanks for your feedback Brett.
An error occurred while saving the comment
Priya Sinha
commented
Hello .. Thanks for your feedback. It is possible though I guess it is not that easily discoverable. You can do it by expanding the database list under alert name in the right hand pane.
An error occurred while saving the comment
Priya Sinha
commented
Hello .. Thanks for your detailed feedback. SQL Monitor does support excluding or including particular database. But I would assume that it is not that discoverable. You can do it by expanding the database list under alert name in the right hand pane. Is this sufficient or are you looking for something else?
-
19 votes
Daniel Rothig
responded
(Gathering feedback)
Hi, is frequency analysis something that we could offer in-app, or would you specifically prefer to export the data first?
An error occurred while saving the comment
Priya Sinha
commented
Thanks a lot for your suggestion Grant.
-
136 votes
An error occurred while saving the comment
Priya Sinha
commented
Thanks a lot for your feedbacl Blaz.
Regards,
PriyaAn error occurred while saving the comment
Priya Sinha
commented
Thanks for your suggestion.
Regards,
PriyaAn error occurred while saving the comment
Priya Sinha
commented
Thanks a lot for the suggestion John.
-
65 votes
Daniel Rothig
responded
For SQL Server perf counters, you can create a Custom Metric against sys.dm_os_performance_counters. For Machine perf counters, you have to use CLI at the moment
An error occurred while saving the comment
Priya Sinha
commented
Thanks for your suggestion Brendo.
Regards,
Priya -
4 votes
-
1 vote
Daniel Rothig
responded
Hi, we’re monitoring a few of those out of the box and the rest can be covered via the custom metrics feature – check out sys.dm_os_performance_counters
An error occurred while saving the comment
Priya Sinha
commented
Hi Don,
Thanks for your suggestion. We will review this soon but for the time being you can use 'Custom metric' feature to start monitoring this particular counter.
Thanks,
Priya -
16 votes
There are currently no plans for a SQL Monitor mobile app. We hope to improve the experience when using SQL Monitor on a mobile device. However at the moment we can’t give a timescale for when this might happen.
An error occurred while saving the comment
Priya Sinha
commented
Thanks for your suggestion.
Regards,
Priya -
35 votes
Daniel Rothig
responded
An error occurred while saving the comment
Priya Sinha
commented
Thanks for your suggestion Edward and Theresa.
Regards,
Priya -
4 votes
An error occurred while saving the comment
Priya Sinha
commented
Hi,
Thanks for your feedback.
Regards,
Priya -
25 votes
Daniel Rothig
responded
We like that idea – if it gains traction, we’ll prioritise it more
An error occurred while saving the comment
Priya Sinha
commented
Hi Matt,
Thanks a lot for your feedback. We will definitely try to improve this area.
Thanks,
Priya -
81 votes
Thanks for the votes and comments on this one. We're actively considering adding replication latency monitoring and alerting to Redgate Monitor.
Since this suggestion was raised, we've added a replication page under Estate tab that lists replication agent jobs with their publisher, distributor, subscriber, publication and job status. It doesn't yet show latency or let you alert on it, but it is something we are considering.
Latency is one of several pieces of replication information customers have asked us for and so it woudl be good to know which of these matter to you:
- Publisher to distributor latency (Log Reader agent delivery latency)
- Distributor to subscriber latency (Distribution agent delivery latency)
- Number of undistributed commands waiting to be applied to each subscriber
- The most recent replication error text for an agent
- + Alerts on any of the above
Please add a comment saying which of these you'd use!
An error occurred while saving the comment
Priya Sinha
commented
Hi John and Nicolaas,
As you may be aware that SQL Monitor now has custom metric and alerts feature. I was just wondering if you have tried writing queries for replication.
If so, would you mind sharing it with us also. You can share your query via this link:
http://sqlmonitormetrics.red-gate.com/share-a-metric/
Thanks,
PriyaAn error occurred while saving the comment
Priya Sinha
commented
Yes, thats the idea. SQL Monitor shows lots of performance counter. We may allow alerting on those .. though it is still being discussed.
An error occurred while saving the comment
Priya Sinha
commented
Thanks John .. for your feedback. For V 3.0, we are currently working on custom alert feature. This feature should allow you to write alerts for replication performance counters.
-
41 votes
An error occurred while saving the comment
Priya Sinha
commented
Thanks Tjay. We do plan to make purge more flexible. Will update you when we start working on this.
Thanks,
Priya -
91 votes
Daniel Rothig
responded
We like the idea – if this idea gains traction, we’ll look into implementing something like this
An error occurred while saving the comment
Priya Sinha
commented
Thanks a lot Steve for your feedback. We will try to add more information about jobs as per your suggestions.
-
69 votes
An error occurred while saving the comment
Priya Sinha
commented
Thanks for confirming. Yes, in this case it wouldn't have worked because you wont be able to restore 2008 backup to 2005.
An error occurred while saving the comment
Priya Sinha
commented
Hello ... thanks for your feedback. Just to clarify, did you change the SQL Monitor data repository database? If this was the case, then migrating this is very easy. The steps could be found here:
Thanks,
Priya -
27 votes
Daniel Rothig
responded
Note that this can set in the BaseMonitor .config file
An error occurred while saving the comment
Priya Sinha
commented
Thanks Mike for your feedback.
An error occurred while saving the comment
Priya Sinha
commented
Hi Andrew .. I have just emailed you. Let me know if you have not received the email.
An error occurred while saving the comment
Priya Sinha
commented
Thanks Andew. The current SQL Monitor released version supports changing the day-time for Index fragmentation checks. Though it is not exposed on UI but can be changed in configuration file.
Would exposing this to UI is enough or do you think that this configuration should be supported per SQL Server?
-
3 votes
An error occurred while saving the comment
Priya Sinha
commented
This is a very good idea. Thanks a lot Kevan.
-
29 votes
An error occurred while saving the comment
Priya Sinha
commented
Hello .. first .. my sincere apologies. Not sure how we missed this post. You should be able to browse history. SQL Monitor doesn't stop browsing history when Suspended. If you think that there is bug then please raise it with Support and we will investigate it.
An error occurred while saving the comment
Priya Sinha
commented
Hi John,
It would be great if you could email the screen shot to priya.sinha@red-gate.com.
Thanks,
PriyaAn error occurred while saving the comment
Priya Sinha
commented
Hello John,
Please help me to understand this issue. The current behaviour for SQL Monitor is that stats for quorum disk is available under "Cluster Overview". The stats for shared disk + quorum disk is also available under current active node. But SQL Monitor always monitors all the nodes of the cluster. So even if the node is not currently active, it is still being monitored. So after failover, you should still be able to see the information.
Please explain bit more in detail.
Thanks a lot,
Priya
Thanks for your suggestion Bill.