I left it over 20 minutes before posting a bug report. When I returned to the server, a {sa} crash had been trapped and sent to Red Gate.
I don't care about the detailed stats as I'll have a fresh set after the cache is rebuilt and the daily Full backups have run. Thanks for the workaround.
MINOR POTENTIAL PROBLEM: one of the SQL Backup instances is on a cluster and the cluster manage is aware of the service - do NOT want to accidentally fail the beast over![Smile]()
Any advice?
Can we say NO to the Cache Compress? I have FIVE more machines to upgrade and don't want to have to fudge around on all ten machines, so far...
I don't care about the detailed stats as I'll have a fresh set after the cache is rebuilt and the daily Full backups have run. Thanks for the workaround.
MINOR POTENTIAL PROBLEM: one of the SQL Backup instances is on a cluster and the cluster manage is aware of the service - do NOT want to accidentally fail the beast over
Any advice?Can we say NO to the Cache Compress? I have FIVE more machines to upgrade and don't want to have to fudge around on all ten machines, so far...