Upgrading SQL instance containing compressed databases

epetro · January 5, 2012 3:04PM

Looks like I will be upgrading an instance of SQL 2005 from SP3 CU10 to SP4 CU3 tomorrow morning.

Unlikely, but if someone sees this between now and then and has information to issues/resolutions/workarounds that they have experienced or discussed, please add to this thread.

I will probably play it safe and take the databases OFFLINE and bring them back ONLINE individually after a final reboot.

Eddie D · January 9, 2012 6:25AM

Hi,
Thank you for your post into the forum and for alerting to me to the fact that we have no Knowledge Base articles giving advice on the actions required on upgrading SQL Server instances when you have compressed database's configured.

Your proposed action of taking the databases off-line and bringing them back on-line after the final re-boot is the best course of action.

We have a KB article on upgrading SQL Storage Compress that recommends this action when upgrading SQL Storage Compress when compressed databases are already present or in-use, which can be viewed using this LINK.

Many Thanks
Eddie

epetro · January 9, 2012 7:53AM

The upgrade to SP4 was successful.
I had SQL related issues with CU3, completely unrelated to Redgate...so I ditched that plan and am comfortable on SP4.

The databases actually came back ONLINE faster than expected.

Eddie D · January 9, 2012 10:42AM

Excellent news that your upgrade was successful.

With the release of SQL Storeage Compress V6 / HyperBac Components V5.4.1.5, improvements were made to increase the performance and reliability when bringing databases back on line. Good to hear that these improvements worked out for you.

Many Thanks
Eddie

Upgrading SQL instance containing compressed databases

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk