4.5 Deploying Reports

You deploy reports to SSRS to make them accessible to anyone using a Web browser. Reporting Center allows you to configure SSRS directly from the Reporting Console. You can deploy either a single report or multiple reports simultaneously to SSRS. When a single report is deployed, you can perform a number of deployment options, such as running the report on a schedule, delivering deployed reports to a file share or an email address. The reports automatically refresh when data changes.

After you deploy a report, Reporting Center automatically deploys changes when you save or run the report in the Console. It is not necessary to manually redeploy a report each time you modify it in the Console, unless you set up a subscription for the report. In that case, when you modify the report in the Console, you must redeploy the report once to reset the subscription. If you delete a deployed report from the Console, it is also deleted from SSRS.

NOTE:To deploy reports from Reporting Center, you must have permission to deploy a report from the Console and you must configure the correct permissions in SSRS. In addition, to take advantage of the email delivery option, you must configure email settings in SSRS.

4.5.1 SSRS Limitations

Before you deploy reports to SSRS, consider the following:

  • For reports deployed using Microsoft SQL Server 2008 Reporting Services, the deployed report does not display the grid lines and tick marks configured in the Reporting Console. You configure grid lines and tick marks in the Properties dialog boxes for the X-Axis, Primary Y-Axis, and Secondary Y-Axis.

  • SSRS does not support the Forecast report property. Consequently, reports configured in Reporting Center using Forecast does not display the forecasted data series.

  • SSRS does not support the Data Point Marker Step report property. When you configure a data point step for markers on a data series, the value of the step is always 1 in SSRS, regardless of the actual value you set the Reporting Console before deploying the report. For more information, see Report Definition Language.

  • If you configure the report in the Deploy Report wizard to automatically refresh at regular intervals and modify the report in the Console, then the following error is displayed when SSRS refreshes the report:

    An error occurred during client rendering. An error has occurred during report processing. The data source ‘DataSourceName’ cannot be found.

    To refresh the report, click F5 in the browser. SSRS resumes the auto-refresh at the intervals specified in the Deploy Report wizard.

4.5.2 Deploying a Report to SSRS

After you have saved a report, you can deploy it to SSRS.

To deploy a report to SSRS and view the deployed report:

  1. From the Reports tab, click Deployment > Deploy Report.

  2. Enter information in the Deploy Report wizard. For more information about the wizard, see the Help.

  3. Click Finish.

  4. To view the deployed report, go to a Web browser and type one of the following URL as applicable:

    • http://ServerName/ReportServer

    • http://ServerName/ReportServer_instance

  5. Click the deployed report.

4.5.3 Deploying multiple Reports to SSRS

You can select multiple reports simultaneously and deploy it to SSRS.

To deploy multiple reports:

  1. From the Quick Access Tool bar, click Deploy Bulk Reports.

  2. In the Bulk Report Deployment, select the required reports.

  3. Select the SQL Server Reporting Services URL. If you want to validate the URL that you have selected, click Validate. To add a new URL of a SQL Server Reporting Server, click AddNewLocation.

  4. Click Deploy Selected.

4.5.4 Using Report Designer to Edit RDL Files

To customize reports, you can also use Report Designer to edit the Report Definition Language (RDL) files for reports you have deployed to SQL Reporting Services. A thorough working knowledge of Report Designer is necessary for making this sort of modification to a report. For more information about using Report Designer, see the Reporting Services Books Online and Microsoft Visual Studio .NET Documentation.