Comments
Sort by recent activity
Thanks for your comment, it's an interesting point. We haven't excluded reportservertempdb because it seems it can have its uses:
The only reason to backup the reportservertempdb is to avoid having to recreate it if there is a hardware failure. In the event of hardware failure, it is not necessary to recover the data in reportservertempdb, but you do need the table structure. If you lose reportservertempdb, the only way to get it back is to recreate the report server database.
https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/backup-and-restore-operations-for-reporting-services
However, we'll give this some consideration to see if it still makes sense, and meanwhile if you raise this as a suggestion on Uservoice it may get additional support.
Regarding the configuration of alerts, we agree this could definitely be improved and we intend to address this later in the year. Apologies for the inconvenience and thanks for your patience.
Adam / comments
Thanks for your comment, it's an interesting point. We haven't excluded reportservertempdb because it seems it can have its uses:
The only reason to backup the reportservertempdb is to avoid havin...
Hi Karl,
This is an area we are exploring how best to improve. Currently you can drag the focus area to show the top 10 over a given time period - in the example screenshot, the table is showing the top 10 blocking processes overnight (from 8pm to 6am). [image]
I'm interested to understand what you would ideally want to be able to do, and what you would do with the output?
Thanks,
Adam / comments
Hi Karl,
This is an area we are exploring how best to improve. Currently you can drag the focus area to show the top 10 over a given time period - in the example screenshot, the table is showing th...
Hi,
We think this sounds like it would be a useful improvement. If you add it as a suggestion on Uservoice and it gets additional support, this would certainly help us prioritise looking further into it.
Were you thinking of something along the lines of how we show this in the Deadlock visualisation below? [image]
Thanks,
Adam / comments
Hi,
We think this sounds like it would be a useful improvement. If you add it as a suggestion on Uservoice and it gets additional support, this would certainly help us prioritise looking further in...
Thanks - I've added your suggestion to that Uservoice item so we can make sure we consider it. / comments
Thanks - I've added your suggestion to that Uservoice item so we can make sure we consider it.
Hi Edvaldo,
Thanks for offering to help, it would be great to get your thoughts - I'll drop you a message so we can arrange a suitable time.
Thanks,
Adam / comments
Hi Edvaldo,
Thanks for offering to help, it would be great to get your thoughts - I'll drop you a message so we can arrange a suitable time.
Thanks,
Adam
Thanks Kevin, I'll drop you a message. / comments
Thanks Kevin, I'll drop you a message.
Thanks for the additional detail - we'll get back to you with more information... / comments
Thanks for the additional detail - we'll get back to you with more information...
Ah okay, in that case, you can view and edit the defaults for the different collections by using the Configuration File editor.
First, locate the configuration file on the machine where the SQL Monitor Base Monitor service is hosted. Location: C:\ProgramData\Red Gate\SQL Monitor
File Name: RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config
Make a copy of this file and name it something useful like RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config_backup
This will act as a backup of the configuration file so that your changes can be reversed.
Next, run the SQL Monitor Configuration Editor as an administrator (right click > Run As):
C:\Program Files\Red Gate\SQL Monitor\BaseMonitor\Tools\ConfigurationFileEditor.exe
You will be prompted to "Load a configuration file". Find the .config file detailed in step 1.
You will be presented with a list of all the configuration options available. These relate to each item in the polling schedule. Any check box which is un-checked automatically uses the default - to check what the default is you can check the box, but not make any changes and the value shown will be the default value.
If you make any changes, once complete, click "Save Changes" and restart the SQL Monitor Base Monitor service. If you have any unexpected results then please delete your edited configuration file and rename the copy (then also restart the service). If you are not making changes, just close without saving.
Does that help?
Thanks,
Adam / comments
Ah okay, in that case, you can view and edit the defaults for the different collections by using the Configuration File editor.
First, locate the configuration file on the machine where the SQL Mon...
Hi,
You can see how many times an alert has been raised (depending on purge settings) in Configuration > Alert settings in the Occurrences column. [image]
You can see the most frequent alerts per server using the Alert Summary Report. [image]
Is this the kind of thing you're looking for? Could you give a bit more detail about what you mean regarding "ones more likely to have larger responses"?
Thanks,
Adam / comments
Hi,
You can see how many times an alert has been raised (depending on purge settings) in Configuration > Alert settings in the Occurrences column.
You can see the most frequent alerts per server us...