Team,
SQL 2008 standard on a Server 2008R2 host
I have an maintenance windows tomorrow and I'd like to bring my version of RedGate up the latest known good release.
However I'm searching for information on the best way to do this
Questions
When I choose check for updates - it comes up as SqlBackup 7.4 Minor release as the only option.
Do I need to stop and services in sql before the upgrade?
Will this require a reboot?
Basically what can I expect so I know how to plan for the upgrade?
If you have detailed instructions those would probally work as well.
But - just saying download and install the upgrade doesn't tell me enough to know what to expect before moving forward.
I've looked through the help file for "Installing or Upgrading on a SQL Server Instance" It's kind of helpful, except I'm having issues with the registered servers - the are mostly not available. I have to keep refreshing to get them connected - but that's only for a few seconds that they stay connected - certainly not log enough for me to setup a log shipping job. I'm pretty sure this is part of the problem that the fix for 3.1.1 fixes. Not sure
Anyway any help would be greatly appreciated.
Thank you
Phygg
SQL 2008 standard on a Server 2008R2 host
I have an maintenance windows tomorrow and I'd like to bring my version of RedGate up the latest known good release.
However I'm searching for information on the best way to do this
Questions
When I choose check for updates - it comes up as SqlBackup 7.4 Minor release as the only option.
Do I need to stop and services in sql before the upgrade?
Will this require a reboot?
Basically what can I expect so I know how to plan for the upgrade?
If you have detailed instructions those would probally work as well.
But - just saying download and install the upgrade doesn't tell me enough to know what to expect before moving forward.
I've looked through the help file for "Installing or Upgrading on a SQL Server Instance" It's kind of helpful, except I'm having issues with the registered servers - the are mostly not available. I have to keep refreshing to get them connected - but that's only for a few seconds that they stay connected - certainly not log enough for me to setup a log shipping job. I'm pretty sure this is part of the problem that the fix for 3.1.1 fixes. Not sure
Anyway any help would be greatly appreciated.
Thank you
Phygg