As we move down this SQL Server 2008 upgrade road I am trying to learn from previous projects of other versions and not take anything for granted. So, I am taking the time to research upgrade paths and issues as we look at moving forward.
First I needed to check and see if there is a supported upgrade path from SQL Server 2008 Enterprise Edition Evaluation to the full licensed product. Indeed there is according to this MSDN article. That may make an in place test to production scenario plausible.
Another MSDN article provide a bunch of food for thought regarding the upgrading of Reporting Services.
In our case, we are needing to upgrade and move servers. From what I have read so far, I am thinking that it would be best to upgrade the existing SSRS 2005 server to 2008 and then move Reporting Services to the new server. This MSDN Article refers to the migration process.
Apparently the Reporting Services database creates stored procedures during its creation that refer to the actual Reporting Services DB name. Because of this, you cannot easily change the Reporting Services database name when moving SSRS to another server.
“You cannot rename the report server database. The identity of the database is recorded in report server stored procedures when the database is created. Renaming either the report server primary or temporary databases will cause errors to occur when the procedures run, invalidating your report server installation.”
Another quirk to our installation is that we use SSL for report delivery. This TechNet article describes the SSL certificate configuration process in SSRS 2008. Keep in mind that since SSRS no longer runs on IIS, having IIS installed on the server running SSRS may complicate life. Specifically when running SSL, also running IIS causes a service dependency.
Popularity: 3% [?]
