Creating a Report Server Database
Reporting Services uses two SQL Server relational databases to store report server metadata and objects. One database is used for primary storage, and the second one stores temporary data. The databases are created together and bound by name. By default, the databases are named reportserver and reportservertempdb. Collectively, the two databases are referred to as the "report server database" or "report server catalog". You can use either SQL Server 2000 or SQL Server 2005 to host the databases.
Important
Do not write applications that run queries against the report server database. The report server database is not a public schema. The table structure might change from one release to the next. If you write an application that requires access to the report server database, always use the Reporting Services APIs to access the report server database.
Server Modes and the Report Server Database
When you create a report server database, you must know in advance whether the report server will be deployed in native mode or SharePoint integrated mode. The contents of the report server database will vary depending on the mode you use. Knowing how the report server will run will determine how you set options when you create the database.
Because native mode is the default, there is no option to select for this mode when you create the database. However, if you deploy a report server in SharePoint integrated mode, you must select the Create the report server database in SharePoint integrated mode option when creating the database.
If you do not select this option, the report server database will only support native mode report server operations. For more information, see How to: Create a Report Server Database for SharePoint Integrated Mode (Reporting Services Configuration).
Ways to Create the Report Server Database
You can create the report server database in the following ways:
- Automatically through Setup, if you choose the default configuration installation option. In the SQL Server Installation Wizard, this is the Install the default configuration option in the Report Server Installation Options page. If you chose the Install but do not configure option, you must use the Reporting Services Configuration tool to create the database.
- Manually through the Reporting Services Configuration tool. For instructions, see How to: Create a Report Server Database (Reporting Services Configuration).
You can create a report server database on a local or remote SQL Server Database Engine instance. Creating the report server database on a remote computer requires that you configure the connection to use a domain user account or a service account that has network access. If you decide to use a remote SQL Server instance, consider carefully which credentials the report server should use to connect to the SQL Server instance. For more information, see Configuring a Report Server Database Connection.
Important
Report Server and the SQL Server instance hosting the report server database can be in different domains. For Internet deployment, it is common practice to use a server that is behind a firewall. If you are configuring a report server for Internet access, use SQL Server credentials to connect to the instance of SQL Server that is behind the firewall and use IPSEC to secure the connection.
Creating Report Server Databases in Different Editions of SQL Server
When creating a report server database, be aware that not all editions of SQL Server 2005 can be used to host the database. The following table shows you which editions of the Database Engine you can use for specific editions of Reporting Services.
| For this edition of SQL Server 2005 Reporting Services | Use this edition of the Database Engine instance to host the database |
|---|---|
SQL Server 2005 Express Edition with Advanced Services |
SQL Server 2005 Express Edition with Advanced Services (local only). |
Workgroup Edition |
Workgroup Edition (local only) |
Evaluation Edition |
Standard, Evaluation, Enterprise Editions (local or remote) |
Developer Edition |
Standard, Developer, Enterprise Editions (local or remote) |
Standard Edition |
Standard, Enterprise Editions (local or remote) |
Enterprise Edition |
Standard, Enterprise Editions (local or remote) |
Creating Report Server Databases on Upgraded Servers
In some cases, you might encounter an exception when you try to create a report server database on an instance of SQL Server that has been upgraded from version 7.0. Upgrading does not set the database compatibility level for the master database. As a result, an exception occurs in the Reporting Services Configuration tool when you set up the database. For more information about how to create the database on an upgraded server, see How to: Configure a Report Server Database on a Database Engine Upgraded from SQL Server 7.0 (Reporting Services Configuration).
See Also
Tasks
How to: Create a Report Server Database (Reporting Services Configuration)
Concepts
Deployment Modes for Reporting Services
Configuring Reporting Services for SharePoint 3.0 Integration
Report Server Database
Administering a Report Server Database
Other Resources
Introducing Reporting Services Programming
Help and Information
Getting SQL Server 2005 Assistance
Change History
| Release | History |
|---|---|
12 December 2006 |
|
14 April 2006 |
|