September 17, 2021 at 2:05 pm
Now that you're on paid SQL 2014, have you configured compression in your backups, since you mentioned storage is a consideration ?
Using a SQL Scheduled job to run backups has fewer "moving parts" to troubleshoot. It can send an alert on failure.
September 20, 2021 at 8:59 pm
Sorry, guess I wasn't completely clear. Space is not a consideration - I have 3 TB of disk space on the machine and less than 1 TB used. The database is only around 100MB - I have ALL backups ever made from the Big Bang onward stored right on the machine, and I still have loads of free space, as well as essentially unlimited network storage, should I want it. (Yes, I also have off-line and off-site copies of the backups.) I programmed the skipping of unnecessary backups just to keep from generating useless stuff, and I zip them as a matter of general tidiness, rather than storage necessity.
But the ability to generate fail reports could be useful. I have not kept up with new features as much as I should, since I have a great deal of other work besides just babysitting this server. Once I get something working, I tend to leave it alone, so there are many new features I could be using, but haven't taken the time to learn.
Thanks for the suggestion - I'll take a look at it.
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy