Activity overview
Latest activity by Brian Harris
SQL Backup 7.6
SQL Backup 7.6 has been released.
This release addresses a security vulnerability identified in SQL Backup 7.4 and 7.5. For more information, see http://www.red-gate.com/sqb76security.
It also incl...
SQL Backup 7.4
We’re pleased to announce that SQL Backup 7.4 has been released and is available to download. This is a minor release and includes new features and bug fixes.New features
- Changes to the Insta...
Hi PDinCA,
Thank you for bringing this to our attention. We're looking into it at the moment. This is not the intended behaviour. The naming format should apply only to new jobs or jobs whose default names you have not previously edited. I can see how the behaviour you're experiencing is very annoying.
Apologies, and we'll do our best to fix this. / comments
Hi PDinCA,
Thank you for bringing this to our attention. We're looking into it at the moment. This is not the intended behaviour. The naming format should apply only to new jobs or jobs whose defau...
The forum for SQL Backup 6.5 has moved
The forum for SQL Backup 6.5 is now in the "Discontinued and Previous Versions" section, lower down this page:http://www.red-gate.com/messageboard/viewforum.php?f=102
SQL Backup 7.0 has been released
We're pleased to announce that SQL Backup 7 has been released. This is a major release and includes new features to make it easy to verify your backups.http://www.red-gate.com/products/dba/sql-back...
Hi,
Thanks for the question. We think that you should be able to just install SQL Monitor v2 on the machine you describe without having to configure any particular roles.
Detailed installation instructions can be found here: http://www.red-gate.com/supportcenter/C ... 134037.htm
Note that this topic also contains various links to other troubleshooting information that may help you set up SQL Monitor.
If you do encounter any issues when attempting the installation, or have further questions, please let us know and we'll address them here.
Regards, / comments
Hi,
Thanks for the question. We think that you should be able to just install SQL Monitor v2 on the machine you describe without having to configure any particular roles.
Detailed installation inst...
Hi Dave,
What you've described is the intended behavior.
Once you have customized an alert at a particular level, changing the alert at a level above in the hierarchy does not overwrite the customized setting. So, in your case, when you have customized the alert for a particular production instance, changing the alert at either the group level, or the All Servers level won't affect that instance.
This is deliberate, as it allows you to set up various exceptions to your basic alert settings - and keep those exceptions even when you tinker with the basic settings.
I think your confusion may arise from the fact that when you customize your instance, the excluded commands are not actually propagated from the higher levels - the "BACKUP" and "DBCC" commands appear in the box as a default starting point for you to adjust the alert. As soon as you set "Customize at this level" though, the connection to any level higher up the hierarchy is broken. So, when you edit the All Servers level, this has NO EFFECT at all on any lower customized levels .
My suggestion is perhaps to do the following:
1. Change the setting for your customized instance to "Inherit settings" and inherit from all servers.
2. Edit the All servers level with your set of exclusions.
3. Go back to your customized instance and set it back to "Customize settings for this level"
4. By default, the same set of exclusions is offered. Add any extra you want. Save the alert.
If you like, we can also raise a feature request for a "Remove all customizations" option at the All Servers level, which will propagate the changes at the top level downwards, and overwrite any customizations?
Hope this makes sense.
Also, maintenance windows are coming very shortly, in version 2.2.
Regds, / comments
Hi Dave,
What you've described is the intended behavior.
Once you have customized an alert at a particular level, changing the alert at a level above in the hierarchy does not overwrite the customi...
Hi,
Regarding the visible length of your database names, you could try the following:
In the Monitored servers list on the left, drill down to the SQL Server instance. Beneath the instances you should now see a list of all the databases on that instance.
You can now click the small plus icon (it's a plus in a small circle opposite the Global Filters list) to increase the width of the Monitored servers list.
This should now allow you to see the names of all your databases. Those with unread alerts are shown in bold and the number of unread alerts in brackets after the name.
It's not quite what you're after, but I hope it may help until we address the issue.
Regds,
Brian Harris
Technical author, SQL Monitor / comments
Hi,
Regarding the visible length of your database names, you could try the following:
In the Monitored servers list on the left, drill down to the SQL Server instance. Beneath the instances you sho...
Hi Sharon,
The next version of SQL Response currently being developed is version 2.0, a major new release with a complete re-design and a range of new features.
There is already a feature request in place for SQL Response to be able to set the frequency of alert email notifications, which will be addressed at v2.0. For reference, this feature request is: SSR-1377.
Announcements about v2.0 will appear on the forums when a public release is available; this won't be for a few months at least.
Redgs,
Brian / comments
Hi Sharon,
The next version of SQL Response currently being developed is version 2.0, a major new release with a complete re-design and a range of new features.
There is already a feature request ...
Hi Sharon,
Yes, that is correct; if an alert is not cleared, no further emails are sent. Only when the alert is cleared, and then re-raised, is a subsequent email triggered. There isn't a way to configure this behaviour in SQL Response at the moment.
As some types of alerts can be raised numerous times, this was a deliberate design decision to stop users being spammed with hundreds of emails relating to multiple occurrences of the same type of problem.
We'll definitely look again at this issue for future versions of SQL Response.
Best regards,
Brian Harris / comments
Hi Sharon,
Yes, that is correct; if an alert is not cleared, no further emails are sent. Only when the alert is cleared, and then re-raised, is a subsequent email triggered. There isn't a way to co...