question

JamesT avatar image
JamesT asked

SQL 2008 R2 Enterprise Downgrade

We currently have SQL2008 R2 Enterprise Edition installed and our licensing is changing to Standard Edition. I need to change the Edition of SQL as well as Integration Services, and Reporting services. Is there a way to install the Standard Edition of SQL2008 R2 and copy the Reporting Services and Integration Services content without uninstalling the Enterprise Edition first? We would like to be able to continue using the packages and reports on the Enteprise Edition until we can migrate all of the content over to the Standard Edition so we do not cause any extended downtime. Thank you for any input or recommendations.
sql-server-2008ssrs-2008
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Tim avatar image
Tim answered
You can install a second instance and migrate to that instance. Not sure how much free storage you have on the server to duplicate any databases and work load or how your applications would react to changing from a default to a named. In the past when I have had to downgrade a server I simply scripted out my users objects, detached my databases, uninstalled the one instance, installed the new, created my user objects and attached the databases. I have to say though that I have not tried this with Reporting Services. Hopefully someone else on here can address the ease or pain of dealing with downgrading Reporting Services. The SQL Engine is pretty straight forward.
1 comment
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

JamesT avatar image JamesT commented ·
Thanks for the info and the conversion to a question for me. We don't have any user databases on this server, we mainly use it for SSIS and SSRS. As you mentioned, the SQL Engine part will be fairly straight forward, I’m mainly concerned about how SSIS and SSRS will respond. Again, thanks for the input.
0 Likes 0 ·
Shawn_Melton avatar image
Shawn_Melton answered
You will have to do a new install as Tim suggested. I would do all this on a test server if possible to make sure it works (cause I have not actually attempted all this): For SSRS follow the migration article [here][1]. There are no differences between editions for SSRS so it should be fairly straightforward to downgrade. You do loose data-driven subscriptions and scale out deployments going down to Standard Edition though. SSIS is all stored in msdb so you will have to restore msdb once you install your Standard Edition instance. The features you loose with it are mostly the advanced adapters. If you do the secondary instance as Tim suggested it should be fairly low downtime as long as no one is creating reports and such. Just restore the databases and then update the SSRS config files to take over the same URL. (notice I did say "should" :) You can check the matrix comparison [here][2] for SQL Server 2008 R2 editions. [1]: http://msdn.microsoft.com/en-us/library/ms143724.aspx [2]: http://msdn.microsoft.com/en-us/library/cc645993.aspx
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

JamesT avatar image
JamesT answered
Based on the information I have received, and the research I have done, it looks like there is no "clean" way to downgrade and retain the default instance name for SQL.( MSSQLSERVER ) This is my current plan of action. (It will require some downtime, but should provide the desired results.) 1. Backup the MSDB database that houses all of the SSIS packages. 2. Backup the Reporting service databases. ( Just in case.. ) 3. Stop reporting services. 4. Detach the SSRS databases as recommended in this MSDN article. ( http://msdn.microsoft.com/en-us/library/ms156421(v=SQL.105).aspx ) 5. Uninstall reporting services. 6. Uninstall SQL2008 Enterprise edition. 7. Reboot the server to clear out any files that were in memory from the old instance. 8. Install SQL2008 Standard edition with SSIS and SSRS. 9. Restore the MSDB that was backed up in step 1. 10. Verify that the SSIS packages are accessible. 11. Test one of the SSIS package to verify that it runs correctly. 12. Attach the SSRS databases as outlined in the MSDN article in step 4. 13. Configure Reporting services to use the attached SSRS databases. 14. Check the reports and verify that they work correctly. I will post an update after the version downgrade to list any issues I run across. Wish me luck !! Thanks again to Tim and Shawn for your assistance.
1 comment
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Shawn_Melton avatar image Shawn_Melton commented ·
You might want to script out any user accounts you have as well. It can depend on the security selected for your SSIS packages if they will work right off once you restore them.
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.