Administering a Report Server Database
Report server database provides internal storage for the report server. The database is created during setup. A temporary database is also created to store session and caching information. The table structure for both databases is optimized for server operations and should not be modified or tuned. Microsoft may change the change table structure from one release to the next. If you modify or extend the database, you may limit or prevent the capability to perform future upgrades or apply service packs. You may also introduce changes that impair report server operations.
All access to a report server database must be handled through the report server. You can use report server management tools (such as Report Manager) or programmatic interfaces such as URL access or the Report Server Web service. To gather metrics about report server performance and activity, see Managing Performance and Querying and Reporting on Report Execution Log Data.
In Reporting Services, database administration refers to backing up and restoring a report server database, and managing the encryption keys that are used to encrypt and decrypt sensitive data.
To administer a report server database, you use a combination of tools:
- SQL Server tools can be used to backup and restore the database (for example, SQL Server Enterprise Manager).
- Report server command line utilities can be used to manage the connection and copy data. You can use Rsconfig utility to manage the connection. If you want to automate administrative tasks or copy data between report server databases, use the Rs utility. For more information, see Deployment and Administration Tools.
The following table describes the topics in this section.
|Storing Encrypted Data in a Report Server Database||Provides information about sensitive and encrypted data stored in a report server database.|
|Managing Encryption Keys||Explains how to back up and restore encryption keys, and how to delete encrypted data that cannot be recovered.|
About the Report Server Temporary Database
Each report server database uses a related temporary database to store session data, cached reports, and work tables that are generated by the report server. The temporary database is bound by the same name as the report server database.
If you delete the temporary database, you must run Setup to create a new version. Reporting Services does not recreate the database if it is missing, nor does it repair missing or modified tables.
You can back up the temporary database if you want to avoid having to run Setup in the event that the temporary database is deleted. If you back up the temporary database and subsequently restore it, you should delete the contents. Generally, it is safe to delete the contents of the temporary database at any time. However, you must restart the report server after you clear the contents.