Migrate a Reporting

Services Installation
(Native Mode)
SQL Server 2014

Native Mode Migration Overview

The migration process for Reporting Services includes manual and automated steps. The
following tasks are part of a report server migration:
Back up database, application, and configuration files.
Back up the encryption key.
Install a new instance of SQL Server 2014. If you are using the same hardware,
you can install SQL Server 2014 side-by-side with your existing installation if it
was one of the supported versions.

Tip

A side-by-side installation may require that you install SQL Server 2014 as a named instance.

Move the report server database and other application files from your existing
installation to your new SQL Server 2014 installation.
Move any custom application files to the new installation.
Configure the report server.
Edit RSReportServer.config to include any custom settings from your previous
installation.
Optionally, configure custom Access Control Lists (ACLs) for the new Reporting
Services Windows service group.
Remove unused applications and tools after you have confirmed that the new
instance is fully operational.
There are restrictions on the editions of SQL Server that host the report server database.
Review the following topic if you are reusing a report server database that was created in
a previous installation.
Create a Report Server Database (SSRS Configuration Manager)
Top

Fixed Database Name

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 causes errors when the procedures run,
invalidating your report server installation.
If the database name from the existing installation is not suited for the new installation,
you should consider creating a new database that has the name, and then load existing
application data using the techniques in the following list:

Write a Visual Basic script that calls Report Server Web service SOAP methods to
copy data between databases. You can use the RS.exe utility to run the script. For
more information about this approach, see Scripting (Reporting Services SSRS).
Write code that calls the WMI provider to copy data between databases. For more
information about this approach, see Access the Reporting Services WMI Provider.
If you have just a few items, you can republish reports, report models, and shared
data sources from Report Designer, Model Designer, and Report Builder to the
new report server. You must re-create role assignments, subscriptions, shared
schedules, report snapshot schedules, custom properties that you set on reports
or other items, model item security, and properties that you set on the report
server. You will lose report history and report execution log data.

Top

Before You Start

Even though you are migrating rather than upgrading the installation, consider running
Upgrade Advisor on your existing installation help identify any issues that could affect
migration. This step is especially helpful if you are migrating a report server that you did
not install or configure. By running Upgrade Advisor, you can find out about custom
settings that might not be supported in a new SQL Server 2014 installation.
In addition, you should be aware of several important changes in SQL Server 2014 that
will affect how you migrate your installation:
Starting with SQL Server 2008, IIS is no longer a prerequisite. If you are migrating
a report server installation to a new computer, you do not need to add the Web
server role. In addition, steps for configuring URLs and authentication are different
from the previous release, as are techniques and tools for diagnosing and
troubleshooting problems.
Report Server Web service, Report Manager, and the Report Server Windows
service are consolidated within a single Report Server service. All three
applications run under the same account. All three applications read configuration
settings from RSReportServer.config file, making RSWebApplication.config
obsolete.
Report Manager and SQL Server Management Studio are redesigned to remove
overlapping features. Each tool supports a distinct set of tasks; the tools are no
longer interchangeable.
ISAPI filters are not supported in SQL Server 2008 Reporting Services and later
versions. If you use ISAPI filters, you must redesign your reporting solution prior to
migration.
IP address restrictions are not supported in SQL Server 2008 Reporting Services
and later versions. If you use IP address restrictions, you must redesign your
reporting solution prior to migration or use a technology such as a firewall, router,
or Network Address Translation (NAT) to configure addresses that are restricted
from accessing the report server.
Client Secure Sockets Layer (SSL) certificates are not supported in SQL Server
2008 Reporting Services and later versions. If you use client SSL certificates, you
must redesign your reporting solution prior to migration.
If you use an authentication type other than Windows Integrated authentication,
you must update the <AuthenticationTypes> element in
theRSReportServer.config file with a supported authentication type. The
supported authentication types are NTLM, Kerberos, Negotiate, and Basic.
Anonymous, .NET Passport, and Digest authentication are not supported in SQL
Server 2008 Reporting Services and later versions.

If you use custom cascading style sheets in your reporting environment, they will
not be migrated. You must manually move them following migration.
For more information about changes in SQL Server 2014 Reporting Services, see the
Upgrade Advisor documentation and What's New (Reporting Services).
Top

Backup Files and Data

Before you install a new instance of Reporting Services, be sure to back up all of the files
in your current installation.
1. Back up the encryption key for the report server database. This step is critical to
migration success. Further on in the migration process, you must restore it for the
report server to regain access to encrypted data. To back up the key, use the
Reporting Services Configuration Manager.
2. Back up the report server database using any of the supported methods for
backing up a SQL Server database. For more information, see the instructions on
how to back up the report server database in Moving the Report Server Databases
to Another Computer (SSRS Native Mode).
3. Back up the report server configuration files. Files to back up include:
a. Rsreportserver.config
b. Rswebapplication.config
c. Rssvrpolicy.config
d. Rsmgrpolicy.config
e. Reportingservicesservice.exe.config
f. Web.config for both the Report Server and Report Manager ASP.NET
applications.
g. Machine.config for ASP.NET if you modified it for report server operations.
Top

Install SQL Server Reporting Services

Install a new report server instance in files-only mode so that you can configure it to use
non-default values. For command line installation, use the FilesOnlyargument. In the
Installation Wizard, select the Install but do not configure option.
Click one of the following links to view instructions on how to install a new instance of
Reporting Services:
Install SQL Server 2014 from the Installation Wizard (Setup)
Install SQL Server 2014 from the Command Prompt
Top

Move the Report Server Database

The report server database contains published reports, models, shared data sources,
schedules, resources, subscriptions, and folders. It also contains system and item
properties, and permissions for accessing report server content.
If your migration includes using a different Database Engine instance, you must move the
report server database to the new Database Engine instance. If you are using the same
Database Engine instance, skip to section Move Custom Assemblies or Extensions.
To move the report server database, do the following:
1. Choose the Database Engine instance to use. SQL Server 2014 Reporting Services
requires that you use one of the following versions to host the report server
database:
o SQL Server 2014
o SQL Server 2012
o SQL Server 2008 R2
o SQL Server 2008

2. Start SQL Server Management Studio and connect to the Database Engine.
3. Create the RSExecRole in the system databases if the Database Engine has
never hosted a report server database. For more information, see Create the
RSExecRole.
4. Follow the instructions in Moving the Report Server Databases to Another
Computer (SSRS Native Mode).
Remember that both the report server database and the temporary database are
interdependent and must be moved together. Do not copy the databases; copying does
not transfer all of the security settings to the new installation. Do not move SQL Server
Agent jobs for scheduled report server operations. The report server will recreate these
jobs automatically.
Top

Move Custom Assemblies or Extensions

If your installation includes custom report items, assemblies, or extensions, you must
redeploy the custom components. If you are not using custom components, skip to
section Configure the Report Server.
To redeploy the custom components, do the following:
1. Determine whether the assemblies are supported or need recompilation:
o Custom authentication extensions created for the SQL Server 2005 release
must be recompiled.
o Custom rendering extensions for SQL Server 2008 Reporting Services must
be rewritten using the Rendering Object Model (ROM).
o HTML 3.2 and HTML OWC renderers are not supported in SQL Server
2008 Reporting Services and later versions.
o Other custom assemblies should not require recompilation.
2. Move the assemblies to the new report server and Report Manager \bin folders. In
SQL Server 2014, the report server binaries are located in the following location
for the default SQL Server 2014 Reporting Services instance:
\Program files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting
Services\ReportServer\bin
3. Modify the configuration files to add entries for your custom component. The
entries will vary depending on the kind of assembly you are using. For instructions
on where to place files and add configuration entries, see the following:
o Deploying a Custom Assembly
o How to: Deploy a Custom Report Item
o Deploying a Data Processing Extension
o Deploying a Delivery Extension
o Deploying a Rendering Extension
o Implementing a Security Extension
Top

Configure the Report Server

Configure URLs for the Report Server Web service and Report Manager, and configure the
connection to the report server database.
If you are migrating a scale-out deployment, take all of the report server nodes offline
and migrate each server one at a time. Once the first report server is migrated and it
successfully connects to the report server database, the report server database version
is automatically upgraded to the SQL Server 2014 database version.

Important

If any of the report servers in the scale-out deployment are online and have not been migrated, they might en
rsInvalidReportServerDatabase exception because they are using an older schema when connected to the up

Note

If the report server you migrated was configured as the shared database for a scale-out deployment, you need
encryption keys from the Keys table in the ReportServer database, before configuring the report server serv
the migrated report server will try to initialize in scale-out deployment mode. For more information, see Add
for Scale-Out Deployment (SSRS Configuration Manager) and Configure and Manage Encryption Keys (SS
The scale-out keys cannot be deleted by using the Reporting Services Configuration Manager. The old keys
the Keys table in theReportServer database using SQL Server Management Studio. Delete all rows in the K
table and prepare it for restoring the Symmetric key only, as documented in the following steps.
Prior to deleting the keys it is recommended you first back up the Symmetric Encryption key. You can use th
Configuration Manager to back up the key. Open the Configuration Manager open, click the Encryption Ke
the Backup button. You can also script WMI commands to back up the encryption key. For more informatio
see BackupEncryptionKey Method (WMI MSReportServer_ConfigurationSetting).
1. Start the Reporting Services Configuration Manager and connect to the Reporting
Services instance you just installed. For more information, seeReporting Services
Configuration Manager (Native Mode).
2. Configure URLs for the report server and Report Manager. For more information,
see Configure a URL (SSRS Configuration Manager).
3. Configure the report server database, selecting the existing report server
database from your previous installation. After successful configuration, the report
server services will restart, and once a connection is made to the report server
database, the database will be automatically upgraded to SQL Server
2014 Reporting Services. For more information about how to run the Change
Database Wizard that you use to create or select a report server database,
see Create a Native Mode Report Server Database (SSRS Configuration Manager).
4. Restore the encryption keys. This step is necessary for enabling reversible
encryption on pre-existing connection strings and credentials that are already in
the report server database. For more information, see Back Up and Restore
Reporting Services Encryption Keys.
5. If you installed report server on a new computer and you are using Windows
Firewall, be sure that the TCP port on which the report server listens is open. By
default, this port is 80. For more information, see Configure a Firewall for Report
Server Access.
6. If you want to administer your native mode report server locally, you need to
configure the operating system to allow local administration with Report Manager.
For more information, see Configure a Native Mode Report Server for Local
Administration (SSRS).
Top

Copy Custom Configuration Settings to

RSReportServer.config File
If you modified the RSReportServer.config file or RSWebApplication.config file in the
previous installation, you should make the same modifications in the new
RSReportServer.config file. The following list summarizes some of the reasons why you
might have modified the previous configuration file and provides links to additional
information about how to configure the same settings in SQL Server 2014.

Customization

Information

Report Server E-mail delivery with

custom settings

Configure a Report Server for E-Mail Delivery (SSRS Configuratio

Configuration Manager (SSRS Native Mode).

Device information settings

Customize Rendering Extension Parameters in RSReportServer.Con

Report Manager on a remote instance

Configure Report Manager (Native Mode)

Top

Windows Service Group and Security ACLs

In SQL Server 2014 Reporting Services (SSRS), there is one service group, the Reporting
Services Windows Service group, which is used to create security ACLs for all the registry
keys, files, and folders that are installed with SQL Server 2014 Reporting Services. This
Windows group name appears in the format
SQLServerReportServerUser$<computer_name>$<instance_name>. This group takes
the place of the two Windows service groups in SQL Server 2005 Reporting Services. If
you have custom ACLs associated with either of the SQL Server 2005 Reporting Services
Windows groups, you will need to apply those ACLs to the new group for your new report
server instance in SQL Server 2014 Reporting Services.
Top

Verify Your Deployment

1. Test the report server and Report Manager virtual directories by opening a
browser and typing in the URL address. For more information, see Verify a
Reporting Services Installation.
2. Test reports and verify they contain the data you expect. Review data source
information to see whether the data source connection information is still
specified. The report server uses the SQL Server 2014 report object model when
processing and rendering reports, but it does not replace SQL Server 2008 or SQL
Server 2008 R2 constructs with new report definition language elements. To learn
more about how existing reports run on a SQL Server 2014 report server,
see Upgrade Reports.
Top

Remove Unused Programs and Files

Once you have successfully migrated your report server to a SQL Server 2014 Reporting
Services instance, you might want to perform the following steps to remove programs
and files that are no longer necessary.
1. Uninstall the previous version of Reporting Services if you no longer need it. This
step does not delete the following items, but you can manually remove them if
you no longer need them:
o The old Report Server database

o RsExec role
o Report Server service accounts
o Application pool for the Report Server Web service
o Virtual directories for Report Manager and the report server
o Report server log files
2. Remove IIS if you no longer need it on this computer.

Moving the Report Server

Databases to Another
Computer (SSRS Native
Mode)
SQL Server 2014

You can move the report server databases that are used in an installation SQL
Server Database Engine to an instance that is on a different computer. Both
thereportserver and reportservertempdb databases must be moved or copied together. A
Reporting Services installation requires both databases; thereportservertempdb database
must be related by name to the primary reportserver database you are moving.
Applies to:Reporting Services Native mode.
Moving a database does not effect scheduled operations that are currently defined for
report server items.

Schedules will be recreated the first time that you restart the Report Server
service.

SQL Server Agent jobs that are used to trigger a schedule will be recreated on the
new database instance. You do not have to move the jobs to the new computer,
but you might want to delete jobs on the computer that will no longer be used.

Subscriptions, cached reports, and snapshots are preserved in the moved

database. If a snapshot is not picking up refreshed data after the database is

moved, clear the snapshot options in Report Manager, click Apply to save your
changes, re-create the schedule, and click Apply again to save your changes.

Temporary report and user session data that is stored in reportservertempdb are
persisted when you move that database.

SQL Server provides several approaches for moving databases, including backup and
restore, attach and detach, and copy. Not all approaches are appropriate for relocating an
existing database to a new server instance. The approach that you should use to move
the report server database will vary depending on your system availability requirements.
The easiest way to move the report server databases is to attach and detach them.
However, this approach requires that you take the report server offline while you detach
the database. Backup and restore is a better choice if you want to minimize service
disruptions, but you must run Transact-SQL commands to perform the operations.
Copying the database is not recommended (specifically, by using the Copy Database
Wizard); it does not preserve permission settings in the database.

Important

The steps provided in this topic are recommended when relocating the report server database is the only cha
installation. Migrating an entire Reporting Services installation (that is, moving the database and changing th
Windows service that uses the database) requires connection reconfiguration and an encryption key reset.

Detaching and Attaching the Report Server

Databases
If you can take the report server offline, you can detach the databases to move them to
the SQL Server instance you want to use. This approach preserves permissions in the
databases. If you are using a SQL Server 2014 database, you must move it to another
SQL Server 2014 instance. After you move the databases, you must reconfigure the
report server connection to the report server database. If you are running a scale-out
deployment, you must reconfigure the report server database connection for each report
server in the deployment.
Use the following steps to move the databases:
1. Backup the encryption keys for the report server database you want to move. You
can use the Reporting Services Configuration tool backup the keys.
2. Stop the Report Server service. You can use the Reporting Services Configuration
tool to stop the service.
3. Start SQL Server Management Studio and open a connection to the SQL Server
instance that hosts the report server databases.

4. Right-click the report server database, point to Tasks, and click Detach. Repeat
this step for the report server temporary database.
5. Copy or move the .mdf and .ldf files to the Data folder of the SQL Server instance
you want to use. Because you are moving two databases, make sure that you
move or copy all four files.
6. In Management Studio, open a connection to the new SQL Server instance that
will host the report server databases.
7. Right-click the Databases node, and then click Attach.
8. Click Add to select the report server database .mdf and .ldf files that you want to
attach. Repeat this step for the report server temporary database.
9. After the databases are attached, verify that the RSExecRole is a database role
in the report server database and temporary database. RSExecRole must have
select, insert, update, delete, and reference permissions on the report server
database tables, and execute permissions on the stored procedures. For more
information, see Create the RSExecRole.
10. Start the Reporting Services Configuration tool and open a connection to the
report server.
11. On the Database page, select the new SQL Server instance, and then
click Connect.
12. Select the report server database that you just moved, and then click Apply.
13. On the Encryption Keys page, click Restore. Specify the file that contains the
backup copy of the keys and the password to unlock the file.
14. Restart the Report Server service.

Backing Up and Restoring the Report Server

Databases
If you cannot take the report server offline, you can use backup and restore to relocate
the report server databases. You must use Transact-SQL statements to do the backup and
restore. After you restore the databases, you must configure the report server to use the
database on the new server instance. For more information, see the instructions at the
end of this topic.

Using BACKUP and COPY_ONLY to Backup the

Report Server Databases
When backing up the databases, set the COPY_ONLY argument. Be sure to back up both
of the databases and log files.

-- To permit log backups, before the full database backup, alter the
database
-- to use the full recovery model.
USE master;
GO
ALTER DATABASE ReportServer
SET RECOVERY FULL
-- If the ReportServerData device does not exist yet, create it.
USE master
GO
EXEC sp_addumpdevice 'disk', 'ReportServerData',
'C:\Program Files\Microsoft SQL
Server\MSSQL12.MSSQLSERVER\MSSQL\BACKUP\ReportServerData.bak'
-- Create a logical backup device, ReportServerLog.
USE master
GO
EXEC sp_addumpdevice 'disk', 'ReportServerLog',
'C:\Program Files\Microsoft SQL
Server\MSSQL12.MSSQLSERVER\MSSQL\BACKUP\ReportServerLog.bak'
-- Back up the full ReportServer database.
BACKUP DATABASE ReportServer
TO ReportServerData
WITH COPY_ONLY
-- Back up the ReportServer log.
BACKUP LOG ReportServer
TO ReportServerLog
WITH COPY_ONLY
-- To permit log backups, before the full database backup, alter the
database
-- to use the full recovery model.
USE master;
GO
ALTER DATABASE ReportServerTempdb
SET RECOVERY FULL
-- If the ReportServerTempDBData device does not exist yet, create it.
USE master
GO
EXEC sp_addumpdevice 'disk', 'ReportServerTempDBData',
'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\BACKUP\ReportServerTempDBData.bak'
-- Create a logical backup device, ReportServerTempDBLog.
USE master
GO
EXEC sp_addumpdevice 'disk', 'ReportServerTempDBLog',
'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\BACKUP\ReportServerTempDBLog.bak'

-- Back up the full ReportServerTempDB database.

BACKUP DATABASE ReportServerTempDB
TO ReportServerTempDBData
WITH COPY_ONLY
-- Back up the ReportServerTempDB log.
BACKUP LOG ReportServerTempDB
TO ReportServerTempDBLog
WITH COPY_ONLY

Using RESTORE and MOVE to Relocate the

Report Server Databases
When restoring the databases, be sure to include the MOVE argument so that you can
specify a path. Use the NORECOVERY argument to perform the initial restore; this keeps
the database in a RESTORING state, giving you time to review log backups to determine
which one to restore. The final step repeats the RESTORE operation with the RECOVERY
argument.
The MOVE argument uses the logical name of the data file. To find the logical name,
execute the following statement: RESTORE FILELISTONLY FROM

DISK='C:\ReportServerData.bak';
The following examples include the FILE argument so that you can specify the file
position of the log file to restore. To find the file position, execute the following
statement: RESTORE HEADERONLY FROM DISK='C:\ReportServerData.bak';
When restoring the database and log files, you should run each RESTORE operation
separately.
-- Restore the report server database and move to new instance folder
RESTORE DATABASE ReportServer
FROM DISK='C:\ReportServerData.bak'
WITH NORECOVERY,
MOVE 'ReportServer' TO
'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\Data\ReportServer.mdf',
MOVE 'ReportServer_log' TO
'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\Data\ReportServer_Log.ldf';
GO
-- Restore the report server log file to new instance folder
RESTORE LOG ReportServer
FROM DISK='C:\ReportServerData.bak'
WITH NORECOVERY, FILE=2
MOVE 'ReportServer' TO
'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\Data\ReportServer.mdf',
MOVE 'ReportServer_log' TO

'C:\Program Files\Microsoft SQL

Server\MSSQL11.MSSQLSERVER\MSSQL\Data\ReportServer_Log.ldf';
GO
-- Restore and move the report server temporary database
RESTORE DATABASE ReportServerTempdb
FROM DISK='C:\ReportServerTempDBData.bak'
WITH NORECOVERY,
MOVE 'ReportServerTempDB' TO
'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\Data\ReportServerTempDB.mdf',
MOVE 'ReportServerTempDB_log' TO
'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\Data\REportServerTempDB_Log.ldf';
GO
-- Restore the temporary database log file to new instance folder
RESTORE LOG ReportServerTempdb
FROM DISK='C:\ReportServerTempDBData.bak'
WITH NORECOVERY, FILE=2
MOVE 'ReportServerTempDB' TO
'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\Data\ReportServerTempDB.mdf',
MOVE 'ReportServerTempDB_log' TO
'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\Data\REportServerTempDB_Log.ldf';
GO
-- Perform final restore
RESTORE DATABASE ReportServer
WITH RECOVERY
GO
-- Perform final restore
RESTORE DATABASE ReportServerTempDB
WITH RECOVERY
GO

How to Configure the Report Server Database

Connection
1. Start the Reporting Services Configuration Manager and open a connection to the
report server.
2. On the Database page, click Change Database. Click Next.
3. Click Choose an existing report server database. Click Next.
4. Select the SQL Server that now hosts the report server database and click Test
Connection. Click Next.

5. In Database Name, select the report server database that you want to use.
Click Next.
6. In Credentials, specify the credentials that the report server will use to connect to
the report server database. Click Next.
7. Click Next and then Finish