Creating a Report Server Database
Note
For SQL Server 2008 R2, there have been no changes to the content that is listed in this topic.
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. With a default SQL Server instance, the databases are named reportserver and reportservertempdb. Collectively, the two databases are referred to as the "report server database" or "report server catalog".
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.
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 native mode default configuration option or the Install the SharePoint integrated mode default configuration 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. You must create the report server database manually if you are using a remote SQL Server Database Engine to host the database. For more information, see How to: Create a Report Server Database (Reporting Services Configuration).
Database Server Version Requirements
SQL Server is used to host the report server databases:
SQL Server 2005 or SQL Server 2008 can be used to host the databases. Do not use SQL Server 2000 or earlier versions of SQL Server.
The SQL Server Database Engine instance can be a local or remote 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.
Database Server Edition Requirements
When creating a report server database, be aware that not all editions of SQL Server 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 Reporting Services |
Use this edition of the Database Engine instance to host the database |
|---|---|
SQL Server Express with Advanced Services |
SQL Server Express with Advanced Services (local only). |
Web |
Web edition (local only) |
Workgroup |
Workgroup edition (local only) |
Evaluation |
Evaluation |
Developer |
Standard, Developer, Enterprise editions (local or remote) |
Standard |
Standard, Enterprise editions (local or remote) |
Enterprise |
Standard, Enterprise editions (local or remote) |