SSRS migration and renaming the ReeportServer database

14 October,2017 by Jack Vamvas

With an existing SQL Server Reporting Services (SSRS) deployment, renaming the ReportServer & ReportServerTempDb databases is not straightforward.

When the ReportServer database is initially created & named, it is created with hard-coded references to the ReportServerTempDb.

There are ways of hacking the stored procedures to point to a new database name – but it’s unsupported – and there is the high risk you will omit changes and create more problems for the service. It is not advisable to use the stored procedure hacking method

If you are migrating ReportServer databases from another installation onto a new SSRS installation – then the most effective way is to migrate the databases and reconfigure SSRS and point to the migrated databases.

It is important to migrate the ReportServer databases as a pair. In other words, the Report Server database and the ReportServer tempdb.

When you’ve migrated the databases to a new SSRS instance – use the rsconfigtool to use the new database.

For a detailed list of instructions use this information:Reporting Services Installation Native Mode

Read More

Business Objects versus SSRS (SQL Server DBA)

The Reporting Server Instance could not be found

 


Author: Jack Vamvas (http://www.sqlserver-dba.com)


Share:

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment on SSRS migration and renaming the ReeportServer database


sqlserver-dba.com | SQL Server Performance Tuning | SQL Server DBA:Everything | FAQ | Contact|Copyright & Disclaimer