Reporting Services Manageability and Deployment Enhancements
SQL Server 2005 offers the following enhancements for managing and deploying Reporting Services.
The Reporting Services Configuration tool is a new server configuration tool that you can use to configure a local or remote report server instance. You can use the tool to configure a report server for first-use, and to maintain the server over time.
Configuration options allow you to configure service accounts, virtual directories, the report server database, scale-out deployment, report server e-mail, and the unattended execution account. You can also use the tool to manage encryption keys. For more information, see Reporting Services Configuration Tool, Configuring Reporting Services Components, and How to: Start Reporting Services Configuration.
SQL Server 2005 Reporting Services includes support for multiple instances, 64-bit installation, and the ability to use local security groups for the service accounts. Reporting Services installation is fully integrated with SQL Server Setup. Setup provides two approaches for installing Reporting Services:
A default configuration option that installs a ready-to-use report server, requiring all server components to be installed locally and use default values.
A files-only installation option that copies the program files to disk. With this option, a report server requires additional configuration before it is available to use. Configuration is now performed separately using the new Reporting Services Configuration tool.
Setup also includes interoperability enhancements that make it easier to deploy a report server on a computer that hosts other Web applications. For example, if you are installing Reporting Services on Microsoft Windows Server 2003, Setup will create a new application pool specifically for the report server Web service. If Windows SharePoint Services is installed on the same computer, Setup will automatically add the report server instance to the SharePoint list of exclusions.
In contrast with earlier versions of Reporting Services, you cannot use Setup to install a scale-out deployment (previously known as "Web farm"), specify a remote report server database, or configure report server e-mail. Scale-out deployment and report server e-mail configuration are performed through the Reporting Services Configuration tool after installation is finished. For more information, see Installing SQL Server Reporting Services and Report Server Installation Options.
You can use SQL Server Management Studio to administer multiple report server instances within the unified Management Studio workspace. You can manage one or more report server instances alongside the other SQL Server services that integrate with Management Studio. For more information, see Introducing SQL Server Management Studio.
You can use the SQL Server Surface Area Configuration tool to determine Report Server Windows service and Web service availability. You can use the Configuration Manager to specify properties on how the Report Server Windows service runs. For more information, see SQL Server Configuration Manager and SQL Server Surface Area Configuration.
Ad hoc report functionality introduces new report model management functionality so that you can securely deploy models and model-driven reports. Several new roles have been added to control access to Report Builder and models. Using SQL Server Management Studio, you can use apply these roles to precisely control access down to the field level. For more information, see Securing Models and Role Assignments for Report Builder Access.