Saving Reports (Report Builder 3.0)
In Report Builder you can save a report to a report server, SharePoint library, file share on which you have write permission, or your computer. You can save a report to the same location from which you opened it, save it to a different location, or save it with a new name to the same or different location. By default, a report is resaved to the location from which you opened it. When you save the report, what you are really saving is the report definition, which describes the report layout. You are not saving the data. Every time you run the report, the report data is refreshed and is likely to be different than the previous time you ran the report.
If you want to save the report to a different format or save the report definition with the data, use one of the following Reporting Services features:
Export a rendered report to a different file format such as comma separated files (CSV) or Excel workbooks and save the report in that format. You can also generate data feeds from reports and save the report data.
Create report subscriptions to deliver and save reports to a file share.
Use report history to save versions of rendered reports as historical copies.
To learn more about viewing and managing reports directly on the report server, see Finding, Viewing, and Managing Reports (Report Builder 3.0 and SSRS) and Administration (Reporting Services) in SQL Server Books Online on msdn.microsoft.com.
Although you can save reports to your computer, saving reports to a report server offers many advantages.
Saving a report to a report server offers the following advantages:
Reports become available to others who have permission to access the folder in which you saved the report.
Reports can be managed and viewed from Report Manager.
Report resources such as data sources, images, and subreports are stored in one place for easier access.
Reports can be delivered to others by subscriptions.
Reports are securely stored in the report server database.
Report runs can be logged and provide performance and auditing information.
Saving a report to a report server is also known as publishing a report. When you save the report, you save the report definition only. Every time you run the report, the report data is refreshed and likely different that the previous time you ran the report. If you want to save the report definition with the data you should use the report history feature. Using this feature, you save a copy of the report with its data.
Many reports use shared data sources, shared datasets, and report models. These items are saved separately on the report server or SharePoint library. When you first create the report, you specify the location of shared data sources, shared datasets, and report models. This information is included in the report definition when you save the report.
If you move shared data sources, shared datasets, or report models to a different folder, report server, or library, the report no longer runs because it cannot connect to the data. To correct the problem you must update and then resave the report. Moving shared data sources, shared datasets, or report models affects reports saved to a report server, SharePoint library, or your computer.
If you have a small number of reports to archive, consider exporting a report and saving it as a file. After you export a report to an application (such as PDF or Excel), you can save it as a file and place it in a protected shared directory on the network. Alternatively, you can upload a saved PDF or Excel file as a resource item if you want to keep all copies of a report, regardless of the format, in the report server database. For more information about exporting a report, see Exporting Reports (Report Builder 3.0 and SSRS) and How to: Upload a File or Report (Report Manager).
If you have a large number of reports to archive, create a subscription that delivers the report directly to the file system. For this approach, you must create a subscription for each report, choose a shared folder to store the reports, and define a schedule that determines when the file is created. Once you define a subscription, the report server can run the report unattended and add report files to the archive using the schedule that you provide. You can also create single-use schedules if you want to archive reports on an occasional basis. For more information about subscriptions and file share delivery, see "File Delivery in Reporting Services" in the Reporting Services documentation in SQL Server Books Online.
You can also use the report history feature to create historical copies. You can then back up the report server database and store the backup in a safe location for future use. All report history (along with reports, shared data source items, folders, subscriptions, and shared schedules) is stored in the report server database. You can create a backup to maintain a permanent copy of report history and metadata such as subscription information that indicates the recipients of a report. For more information, see "Managing Report History" in the Reporting Services documentation in SQL Server Books Online.