Installing Reporting Services
A primary component of a Reporting Services solution happens at the initial installation. This has never been truer than with this release, with the rapidly expanding suite of features available through SharePoint integrated mode. Although using Reporting Services in native mode still delivers a sophisticated set of functionality, the focus of the latest edition of SQL Server adds many new features to SharePoint integrated installations.
A Reporting Services native mode instance can run on the same hardware as the relational database but doesn't need to if the system load requires scale-out. For more information on scale-out reporting solutions, see http://sqlcat.com/sqlcat/b/technicalnotes/archive/2008/06/05/reporting-services-scale-out-architecture.aspx. Installing the server in native mode creates one Windows service and installs two relational databases: one that contains deployed report definitions and other metadata, and a second for temporary objects used in processing. After installation, be sure to visit the Reporting Services Configuration Manager to adjust settings, back up the encryption keys, and save them in a safe place. Keeping all the metadata in the ReportServer database makes it simple to back up, but without the encryption key a restore is difficult.
If you have chosen native mode in the installation program of SQL Server, you should choose a service account under which Reporting Services will run. You also should install ...