1. Backup the report server database and report server temporary database. By default, the databases are named reportserver$SQLExpress and reportserverTempDB$SQLExpress.

2. Backup the RSReportServer.config file. If you modified other configuration files (such as Web.config or RSWebApplication.config), you should back them up.

3. Backup the encryption key using the Encryption Keys page in the Reporting Services Configuration tool. For more information, see Backing Up and Restoring Encryption Keys.

4. Run Setup with the SKUUPGRADE=1 argument.

   To run Setup in unattended mode from the command line, use syntax that is similar to the following example. Note that the PIDKEY is fictitious; be sure to replace it with a PIDKEY that is valid for the edition you are installing.

   	Copy Code
   start /wait setup.exe ADDLOCAL=SQL_Engine,RS_Server PIDKEY=ABCDE12345FGHIJ67890KLMNO INSTANCENAME=SQLEXPRESS UPGRADE=SQL_Engine,RS_Server SKUUPGRADE=1 /qb

   To run the SQL Server Setup Wizard:

   1. Open a command prompt, navigate to the directory or drive that contains the installation media, and specify setup.exe SKUUPGRADE=1 on the command line (for example, d:\setup.exe SKUUPGRADE=1).
      
   2. On the Registration Information page, enter identification information used to register your copy of SQL Server.
      
   3. On the Components to Install page, select Database Services, Reporting Services, and Workstation components, Books Online and development tools.
      
   4. On the Instance Name page, click Named instance, and then choose the SQLEXPRESS instance you are upgrading.
      
   5. Complete the wizard by specifying options on the remaining pages.
      

5. Apply Service Pack 1 after Setup is complete.

To verify that the upgrade succeeded, open Report Manager. You should be able to view all of the reports that you previously created. If you have not changed the virtual directory, the URL used to access Report Manager in the upgraded installation will be the same URL you used in the Express installation.

Unless you rename them, an upgraded installation continues to use names from the original installation. If you used default SQL Server Express names, the upgraded SQL Server instance name continues to be <servername>\SQLExpress. For the databases, the default names continue to be reportserver$sqlexpress and reportservertempdb$sqlexpress. For the Reporting Services URLs, the default names continue to be http://<servername>/reports$SQLExpress and http://<servername>/reportserver$SQLExpress. To avoid confusion, you can reregister the SQL Server instance to change the instance name, and rename the report server virtual directories. Renaming a report server database is not supported. For more information, see Registering Servers and Configuring Report Server Virtual Directories in SQL Server Books Online.

In addition to viewing existing report server content, you should also be able to create subscriptions and scheduled operations, and use other features that are available in the edition you installed. For more information about how to create subscriptions and schedules, see Report Manager How-to Topics. If the report server upgrade did not succeed or seems incomplete, you can migrate the installation instead. For more information, see Migrating Reporting Services.

You can specify client components on the command line to upgrade SQL Server Management Studio and Business Intelligence Development Studio. You can verify whether the tools upgraded correctly by doing the following:

• Connect to a Reporting Services instance in SQL Server Management Studio.
  
• Create additional project types in Business Intelligence Development Studio (specifically, the Report Model project template should be available when you create a new project in Business Intelligence Development Studio).
  

If the tools do not upgrade correctly, you can use Add or Remove Programs to uninstall the tools you no longer need, and then run SQL Server Setup to install the tools that are included in the edition you are upgrading to.

If you are migrating other SQL Server Express databases that provide data to reports to another Database Engine, be sure to update the data source connection information used by published reports after the upgrade is complete. For example, if a data source specified Data Source=localhost\sqlexpress, it should be updated to Data Source=localhost if you migrate the database to a local default instance.

Tasks

Concepts