September 3, 2013 at 6:29 am
Sometime in the next few weeks or so, I'm going to be migrating an SSRS server from one machine to another. The reporting service DBs live on a separate SQL box, which is NOT being changed.
My question, is what will I need to do to migrate the existing reports that devs and users have created to this new server? Or, do the reports "live" in the databases, and all I'll need to do is point the new SSRS to the "old" dbs and be done? If the reports live on the filesystem of the SSRS box, where can I find them, and can I simply copy them to the new SSRS box (once I load an instance of SSRS with the same settings as the old)?
Thanks,
Jason
September 3, 2013 at 7:40 am
hi there,
Which SSRS are you moving? 2000, 2005, 2008 or 2012?
September 3, 2013 at 7:56 am
We're running SSRS 2008R2, and will still be on SSRS 2008R2. It's the OS that's getting updated.
September 3, 2013 at 8:06 am
Use the Repoting services configuration manager on the system you want to move.
Backup the RS encryption cert . Backup the RS and RSTEMPdb with copy.
Install SSRS on new machice. Restore original db from server RS and RStemp. Use SSRS config manager to restore the cert.
Make sure dbs referenced in the data soiurces are present on the server.
Restart SSRS services.
Lots of information on the net for this process.
September 3, 2013 at 8:08 am
On the current application server where your reporting services is installed,
do the following
http://www.mssqltips.com/sqlservertip/1453/sql-server-reporting-services-configuration-tool/
start Reporting Services Configuration
1.Click Start, point to All Programs, point to Microsoft SQL Server 2008 R2, and then point to Configuration Tools.
If you want to configure a report server instance from a previous version of SQL Server, open the program folder for that version. For example, point to Microsoft SQL Server 2005 instead of Microsoft SQL Server 2008 R2 to open the configuration tools for SQL Server 2005 server components.
2.Click Reporting Services Configuration Manager. The Connect to a Report Server Instance dialog box appears so that you can select the report server instance you want to configure.
3.In Server Name, specify the name of the computer on which the report server instance is installed. The name of the local computer appears by default, but you can type the name of a remote SQL Server instance if you want to connect to a report server that is installed on a remote computer.
4.If you specify a remote computer, click Find to establish a connection.
5.In Report Server Instance, select the SQL Server Reporting Services instance that you want to configure. Only report server instances for this version of SQL Server appear in the list. You cannot configure earlier versions of Reporting Services.
6.Click Connect.
September 3, 2013 at 8:25 am
Talib123 (9/3/2013)
Use the Repoting services configuration manager on the system you want to move.Backup the RS encryption cert . Backup the RS and RSTEMPdb with copy.
Install SSRS on new machice. Restore original db from server RS and RStemp. Use SSRS config manager to restore the cert.
Make sure dbs referenced in the data soiurces are present on the server.
Restart SSRS services.
Lots of information on the net for this process.
So, based on this, the reports do "live" in the ReportServer databases? As long as I make sure to backup the encryption key(s,) take a backup of the DBs (just in case, remember, the SQL Server hosting the DBs is a separate machine which is NOT being changed,) then load up the new machine, restore the cert(s), and I should be good to go?
Well, other then the Devs and users changing their Reporting Services connections...
Jason
September 3, 2013 at 8:39 am
So, based on this, the reports do "live" in the ReportServer databases? As long as I make sure to backup the encryption key(s,) take a backup of the DBs (just in case, remember, the SQL Server hosting the DBs is a separate machine which is NOT being changed,) then load up the new machine, restore the cert(s), and I should be good to go?
Well, other then the Devs and users changing their Reporting Services connections...
Jason
Since your ReportServer databases are on a different server you don't need to back up the db. Just back up the encryption key(s,) on the current machine, install reporting services on the new machine and point the database to the existing DB and then restore the encryption key(s,).
For your anticipated question. Yes the actual reports live in the ReportServer database table called catalog, incase you wanna browse it.
September 3, 2013 at 8:44 am
Paranoia says back up the DBs, even if they shouldn't need it...
😀
Cool, thanks. No I have no intention of trying to browse the DB itself.
Thanks!
Jason
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply