Skip to content

Latest commit

 

History

History
103 lines (64 loc) · 7.85 KB

ssrs-report-server-create-a-report-server-database.md

File metadata and controls

103 lines (64 loc) · 7.85 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic ms.custom
Create a report server database, Configuration Manager
SQL Server Reporting Services native mode 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.
kfollis
kfollis
09/25/2024
reporting-services
report-server
conceptual
updatefrequency5

Create a report server database, Report Server Configuration Manager

[!INCLUDE ssrs-appliesto] [!INCLUDE ssrs-appliesto-2016-and-later] [!INCLUDEssrs-appliesto-pbirsi] [!INCLUDEssrs-appliesto-sharepoint-2013-2016i]

[!INCLUDE ssrs-previous-versions]

SQL Server [!INCLUDEssRSnoversion] native mode uses two [!INCLUDEssNoVersion] 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 [!INCLUDEssNoVersion] instance, the databases are named reportserver and reportservertempdb. Collectively, the two databases are called the report server database or report server catalog.

::: moniker range="=sql-server-2016"

SQL Server [!INCLUDEssRSnoversion] SharePoint mode includes a third database that's used for data alerting metadata. The three databases are created for each SSRS service application. The database names by default include a GUID that represents the service application.

The following are example names of the three SharePoint mode databases:

  • ReportingService_90a9f37075544f22953c4a62e4a9f370

  • ReportingService_90a9f37075544f22953c4a62e4a9f370TempDB

  • ReportingService_90a9f37075544f22953c4a62e4a9f370_Alerting

::: moniker-end

Important

Don't write applications that run queries against the report server database. The report server database isn't 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 SQL Server [!INCLUDEssRSnoversion] APIs to access the report server database.

Execution log views are exceptions to this rule. For more information, see Report Server ExecutionLog and the ExecutionLog3 View.

Ways to create the report server database

Native mode

You can create the native mode report server database in the following ways:

  • Automatic. Use the SQL Server setup wizard if you choose the default configuration option for installation. In the SQL Server Installation Wizard, this option is Install and configure on the Report Server Installation Options page. If you choose the Install only option, you must use SQL Server Report Server Configuration Manager to create the database. (Applies only to SQL Server Reporting Services 2016 and earlier)

  • Manual. Use SQL Server [!INCLUDEssRSnoversion] Configuration Manager. Create the report server database manually if you use a remote [!INCLUDEssDEnoversion] to host the database. For more information, see Create a Native Mode Report Server Database.

::: moniker range="=sql-server-2016"

SharePoint mode

The Report Server Installation Options page has only one option for SharePoint mode, Install Only. This option installs all the SQL Server [!INCLUDEssRSnoversion] files and the SQL Server [!INCLUDEssRSnoversion] shared service. The next step is to create at least one SSRS service application in one of the following ways:

::: moniker-end

Database server version requirements

[!INCLUDEssNoVersion] is used to host the report server databases. The [!INCLUDEssDEnoversion] instance can be local or remote. The following supported versions of [!INCLUDEssDEnoversion] can host the report server databases:
::: moniker range=">=sql-server-ver15"

  • Azure SQL Managed Instance

  • SQL Server 2022

  • SQL Server 2019

::: moniker-end ::: moniker range=">=sql-server-2017"

Note

SQL on Linux isn't a supported environment to host a SQL Server Reporting Services database.

If you create the report server database on a remote computer, configure the connection to use a domain user account or a service account that has network access. If you use a remote [!INCLUDEssNoVersion] instance, consider which credentials the report server should use to connect to the instance. For more information, see Configure a Report Server Database Connection (Report Server Configuration Manager).

Important

The report server and the [!INCLUDEssNoVersion] instance hosting the report server database can be in different domains. For internet deployment, it's common practice to use a server that's behind a firewall.

If you configure a report server for internet access, use [!INCLUDEssNoVersion] credentials to connect to the instance of [!INCLUDEssNoVersion] that's behind the firewall. Secure the connection by using IPSEC.

Edition requirements for a database server

When you create a report server database, not all editions of [!INCLUDEssNoVersion] can be used to host the database. For more information, see Edition requirements for the report server database in SQL Server Reporting Services features supported by its editions.

Related content