Saving Reports (Report Builder 2.0)
In Report Builder 2.0, you save a report definition to the same location from which you opened it. You can also save it with a new name. In addition, you can save it as a rendered report in several ways. A report server does not provide document management features for formally archiving your reports; however, you can use one of the following approaches to save and share rendered reports.
If you have a small number of reports to archive, consider saving a report 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 2.0) and How to: Upload a File or Report in Report Manager (Report Builder 2.0).
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.
Log information is not stored in report server database. If you require a permanent record of report runs, you must back up the log files separately. For more information, see "Auditing and Verifying Report Runs" and "Managing Report Server Content" in the Reporting Services documentation in SQL Server Books Online.