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. 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".
Reporting Services SharePoint mode includes a third database that is used for data alerting metadata. The three databases are created for each Reporting Services service application and the database names by default include a guid that represents the service application. The following are example names of the three SharePoint mode databases:
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.
The exception to this are the execution log views. For more information, see Report Server Execution Log and the ExecutionLog3 View
Native Mode: You can create the Native mode report server database in the following ways:
Automatically: Use SQL Server Setup Wizard, if you choose the default configuration installation option. In the SQL Server Installation Wizard, this is the Install and configure in the Report Server Installation Options page. If you chose the Install only option, you must use the Reporting Services Configuration Manager to create the database.
Manually: Use the Reporting Services Configuration Manager. 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 Create a Native Mode Report Server Database (SSRS Configuration Manager).
SharePoint Mode: The Report Server Installation Options page only has one option for SharePoint mode of Install Only. This option installs all the Reporting Services files and the Reporting Services shared service. The next step is to create at least one Reporting Services service application in one of the following ways:
Use SharePoint Central Administration to create a Reporting Services service application. For more information see the “Service Application” section of Step 3: Create a Reporting Services Service Application.
Use Reporting Services PowerShell cmdlets to create a service application and the report server databases. For more information see the sample for creating service applications in the topic PowerShell cmdlets for Reporting Services SharePoint Mode.
SQL Server is used to host the report server databases. The SQL Server Database Engine instance can be a local or remote instance. The following are the supported versions of SQL Server Database Engine that can be used to host the report server databases:
SQL Server 2016 Community Technology Preview 2 (CTP2)
SQL Server 2014
SQL Server 2012
SQL Server 2008 R2
SQL Server 2008
SQL Server 2005
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 Configure a Report Server Database Connection (SSRS Configuration Manager).
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.
When creating a report server database, be aware that not all editions of SQL Server can be used to host the database. For more information, see the “Report Server Database Server Edition Requirements” section of Features Supported by the Editions of SQL Server 2016.