SQL Server reportserver and reportservertempdb

The SSRs directory contains two databases:

Report Server Database (default name: reportserver) and reportserver temporary database (default name: reportservertempdb ).

The Report Server database is an SQL Server database.

It can store SSRs configurations, report Definitions, report metadata, report history, cache policies, snapshots, resources, security settings, encrypted data, schedule and submit data, and extended information. Note that although you can directly access the database under the SSRs directory and directly modify the objects used by the SSRS, it is not recommended (or not supported) in practice, because the internal data and structure under the SSRs directory cannot be guaranteed to be compatible with different versions of SSRs, service packages, or patches. Treat the Report Server database as one of the product databases. Although many developers are used to store RDL in a separate warehouse, which leads to frequent recovery of RDL, the loss of snapshot data can bring negative business impact. For example, you may use the snapshot report's "relatively static" data capability to make some business decisions.

Another database used by SSRs is the temporary Report Server database.

This database stores intermediate processing products, such as buffered reports, sessions, and execution data. Note: To store temporary snapshots in the file system rather than in the database, the administrator should complete the following steps. First, modify rsreportserver. config and set webserviceusefile1_storage and windowsserviceusefile1_storage to true. Then, set file1_storagelocation to a full name path. The default path is "C: \ Program Files \ Microsoft SQL Server \ mssql.3 \ Reporting Services \ rstempfiles ". Unlike SQL Server's tempdb, when the data storage time limit in reportservertempdb exceeds SQL Server, the report server restarts. In addition, the Report Server can periodically clear expired and isolated data in reportservertempdb. All data in reportservertempdb can be deleted at any time with minimal or no impact.

For example, the minimal impact that such users may experience is temporary performance degradation (because cache data is lost and an execution state is lost ). The execution status is stored in the sessiondata table. The loss of execution status results may cause an error: "execution 'j4j3vfblcanzv3qzcqhvml55' cannot be found (rsexecutionnotfound )". To solve the loss of execution status, you need to open a report again. The system prompts that SSRs cannot restore the reportservertempdb or table deleted from the database. To quickly restore objects from the database by deleting errors, a script or an empty reportservertempdb backup should be retained. In an extended release, the SSRs directory is shared across all reporting servers in the release.