Native Mode Reporting Services uses a SQL Server database for internal storage. The database is required and it is used to store published reports, models, shared data sources, session data, resources, and server metadata.
To create a report server database or to change the connection string or credentials, use the options in the Database page in the Reporting Services Configuration Manager.
You must create and configure the report server database if you installed the report server in files-only mode.
If you installed Reporting Services in either the default configuration for native mode, the report server database was created and configured automatically when the report server instance was installed. You can use the Reporting Services Configuration Manager to view or modify the settings that Setup configured for you.
To enable access to a remote report server database
If you are using a remote Database Engine instance, log on to the database server to verify or enable TCP/IP connections.
Point to Start, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and click SQL Server Configuration Manager.
Open SQL Server Network Configuration.
Select the instance.
Right-click TCP/IP and click Enabled.
Restart the service.
Open your firewall software and open the port that SQL Server listens on. For the default instance, this is typically port 1433 for TCP/IP connections. For more information, see Configure a Windows Firewall for Database Engine Access in SQL Server Books Online.
To create a local report server database
Start the Reporting Services Configuration Manager and connect to the report server instance for which you are creating the database. For more information, see How to: Start the Reporting Services Configuration Tool.
On the Database page, click Change Database.
Click Create a new report server database, and then click Next.
Connect to the instance of the Database Engine that you will use to create and host the report server database:
Type the SQL Server Database Engine instance that you want to use. The wizard will display a local Database Engine that runs as the default instance if it is available. Otherwise, you must type the server and instance to use. Named instances are specified in this format: <servername>\<instancename>.
Enter the credentials used for a one-time connection to the Database Engine for the purpose of creating the report server databases. For more information about how these credentials are used, see Before You Start in this topic.
Click Test Connection to validate the connection to the server.
Specify properties used to create the database. For more information about how these properties are used, see Before You Start in this topic:
Type the name of the report server database. A temporary database is created along with the primary database. Consider using a descriptive name to help you remember how the database is used. Note that the name you specify will be used for the lifetime of the database. You cannot rename a report server database after it is created.
Select the language in which you want role definitions and My Reports to appear.
The Report Server Mode is always set to Native.
Specify the credentials used by the report server to connect to the report server database.
Specify the authentication type:
Select Database Credentials to connect using a SQL Server database login that is already defined. Using database credentials is recommended if the report server is on a computer that is in a different domain, a non-trusted domain, or behind a firewall.
Select Windows Credentials if you have a least-privileged domain user account that has permission to log on to the computer and the database server.
Select Service Credentials if you want the report server to connect using its service account. With this option, the server connects using integrated security; credentials are not encrypted or stored.
Review the information on the Summary page to verify the settings are correct, and then click Next.
Verify the connection by clicking a URL on the Report Server URL page or Report Manager URL page. The URLs must be defined in order for this test to work. If the report server database connection is valid, you will see either the report server folder hierarchy or Report Manager in a browser window. For more information, see Verify a Reporting Services Installation in SQL Server Books Online.