Comments
Sort by recent activity
Thank you for your post.
At the moment it is not possible to ignore negative deviations in the Job Duration Unusual alert. I have made a note of this though and have passed it to the development team. Could I ask you to post a suggestion to the SQL Monitor UserVoice forum, which is where the team gauge user interest in suggestions. https://sqlmonitor.uservoice.com/forums ... uggestions / comments
Thank you for your post.
At the moment it is not possible to ignore negative deviations in the Job Duration Unusual alert. I have made a note of this though and have passed it to the development t...
The more simple the regular expression the better. If you select the blue '?' next to the field it gives you some examples, including [Bb]ackup which will match both 'backup' and 'Backup'. There is also two links to some help there. / comments
The more simple the regular expression the better. If you select the blue '?' next to the field it gives you some examples, including [Bb]ackup which will match both 'backup' and 'Backup'. There ...
As I mentioned in my post, we expect a small number of deadlocks to happen given the volumes of data that can be processed. SQL Monitor has been designed to cope with them and ensure that there is no loss of data or impact on the UI as this cause a smaller performance impact than trying to completely prevent them. But more frequent deadlocks can be an indication of other ongoing issues.
Can you therefore, both of you, email support@red-gate.com to raise a support ticket with the following information:
- The SQL Monitor error logs. Navigate to Configuration > About and select Retrieve all logs.
- an example deadlock alert. I am specifically interested in the Deadlock Graph as it will be interesting to see the processes involved and the resources.
- confirmation about whether these are new issues, or you saw the with version 3 too. / comments
As I mentioned in my post, we expect a small number of deadlocks to happen given the volumes of data that can be processed. SQL Monitor has been designed to cope with them and ensure that there is...
Thank you for your post.
Due to the huge amounts of data that SQL Monitor can process, especially for elements like the top queries, there is always the risk of deadlocks at busy times. During development the development team realised that to prevent deadlocks would cost performance in the tool. So they instead implemented some functionality that makes sure that the deadlocks are as short as possible and that there is no loss of collected data. They have also been able to ensure that the UI should show no ill effects when a deadlock is encountered.
The deadlock that you have quotes looks to be one of these 'normal' deadlocks that can occur at busy times. If they are occurring very frequently then this can be an indication of a performance problem. But in themselves they shouldn't be anything to worry about.
I hope that this makes sense. If you have any questions then please let me know. / comments
Thank you for your post.
Due to the huge amounts of data that SQL Monitor can process, especially for elements like the top queries, there is always the risk of deadlocks at busy times. During dev...
The log file is likely to be too ungainly to be posted here. Please email support@red-gate.com with the log file and quote this forum post. / comments
The log file is likely to be too ungainly to be posted here. Please email support@red-gate.com with the log file and quote this forum post.
I'm sorry for the delay in replying.
If you right-click on the tools title bar, you should see the option "Minimum Logging Levels: (no logging) ...". Select this and then select "Verbose". Unfortunately you will then need to reproduce the problem that you had before, but it should log the activity. Once you have reproduced the problem either select "Locate Log files..." or "Open current log file...". Please feel free to email support@red-gate.com with the log file and quoting this forum post. / comments
I'm sorry for the delay in replying.
If you right-click on the tools title bar, you should see the option "Minimum Logging Levels: (no logging) ...". Select this and then select "Verbose". Unfort...
The data repository database contains all the collected data, configuration and settings used by the tool. The ultimate size of the database is influenced by the number of machines/sql server instances being monitored, the number of alerts being generated and the data purge settings used.
The information in the data sheet is simply a guide and true information for a given environment can only be obtained in the field. / comments
The data repository database contains all the collected data, configuration and settings used by the tool. The ultimate size of the database is influenced by the number of machines/sql server inst...
Thank you for your post.
The Query Duration is the time from the Query start time that the query finished. This is not necessarily the execution time though / comments
Thank you for your post.
The Query Duration is the time from the Query start time that the query finished. This is not necessarily the execution time though
Thank you for your post.
Please can you email support@red-gate.com with the following information so that we can investigate
- the SQL Monitor error log files: https://documentation.red-gate.com/page ... d=20743048
- a screenshot showing exactly what you are seeing. / comments
Thank you for your post.
Please can you email support@red-gate.com with the following information so that we can investigate
- the SQL Monitor error log files:https://documentation.red-gate.com/pag...
Thank you for your post and I am sorry for the delay in replying.
If you navigate to the Configuration > Alert Settings page then you can select entities from the tree on the left hand side of the page. The list of applicable alert settings will change accordingly and any changes to the configuration will override the global settings for the select entity.
However, the information for the deadlock alert is collected from the SQL Server directly, and it is only when SQL Monitor performs processing on the deadlock graph that it works out which processes were involved. This means that it is not possible to configure these alerts to exclude specific databases but only specific SQL Server instances. / comments
Thank you for your post and I am sorry for the delay in replying.
If you navigate to the Configuration > Alert Settings page then you can select entities from the tree on the left hand side of the ...