Microsoft SQL Server Product Samples: Reporting Services

New Post: Sample Reports still using 2005 DB

mariwill — Fri, 11 Jul 2008 19:55:52 GMT

The reports have been rewritten to use AdventureWorks2008 and show new Reporting Services features. The updated version is expected to be available the end of July.
Marianne

New Post: Sample Reports still using 2005 DB

bci — Tue, 01 Jul 2008 15:13:20 GMT

I downloaded the Sample Reports that are tagged as being for SSRS 2008 RC0 however when I installed them they are still the 2005 version. When I open the project it still converts them to 2008 and when I deploy the project it still uses the 2005 data sources. IE It looks for AdventureWorks instead of AdventureWorks2008.

I was able to run the reports by pointing the datasource to AdventureWorks2008 however I was wondering if there are plans to have an actual 2008 version? It is a little confusing since the reports are listed as the 2008 release however they seem to be exactly the same as the 2005 release.

Source code checked in, #11622

ReedMe — Wed, 11 Jun 2008 05:42:45 GMT

Adding 'Katmai:June 2008 RC0'

Updated Wiki: Home

ReedMe — Tue, 10 Jun 2008 23:51:30 GMT

SQL Server Samples Portal Page > SQL Server Reporting Services Product Samples

SQL Server 2008 RC0 product samples are now available.

SQL Server Reporting Services is a comprehensive, server-based solution that enables the creation, management, and delivery of both traditional, paper-oriented reports and interactive, Web-based reports. An integrated part of the Microsoft business intelligence framework, Reporting Services combines the data management capabilities of SQL Server and Microsoft Windows Server with familiar and powerful Microsoft Office System applications to deliver real-time information to support daily operations and drive decisions.

This project contains Reporting Services samples released with Microsoft SQL Server product. These samples are in the following five categories: Application Samples, Extension Samples, Model Samples, Report Samples, and Script Samples. If you are interested in contributing Reporting Services samples, please let us know by posting in the developers' forum.

To download these samples click on the Releases tab (or click here), optionally select another (older) release, then click on the Windows Installer package (MSI file) which matches the architecture of the installation computer.

For information about how to use CodePlex to access SQL Server samples, click here.
To download samples databases, click here and then click the appropriate MSI file.
For release notes and brief descriptions of all the sample databases and code, including restrictions on SQL Express and Vista, click here.

Application Samples

Sample	SQL Server 2005	SQL Server 2008
AsynchronousRender Sample Windows Application	SS2005	SS2008
FindRenderSave Sample Windows Application	SS2005	SS2008
ReportSearch	SS2005	SS2008
RSExplorer Sample Application	SS2005	SS2008

Extension Samples

Sample	SQL Server 2005	SQL Server 2008
Custom Report Item Sample	SS2005	SS2008
File Share Data Processing Extension Sample	SS2005	SS2008
Printer Delivery Extension Sample	SS2005	SS2008
Security Extension Sample	SS2005	SS2008

Model Samples

Sample	SQL Server 2005	SQL Server 2008
AdventureWorks Sample Model	SS2005	SS2008

Report Samples

Sample	SQL Server 2005	SQL Server 2008
AdventureWorks Sample Reports	SS2005	SS2008
AdventureWorksOffline Report Samples	n/a	SS2008
Report Builder Report Samples	SS2005	SS2008
Server Management Sample Reports	SS2005	SS2008

Script Samples

Sample	SQL Server 2005	SQL Server 2008
Script Samples (Reporting Services)	SS2005	SS2008

UPDATED RELEASE: SQL Server 2008 RC0 (Jun 10, 2008)

Tue, 10 Jun 2008 23:35:04 GMT

This release contains the SQL Server 2008 RC0 product samples for Reporting Services.

RELEASED: SQL Server 2008 RC0 (Jun 10, 2008)

Tue, 10 Jun 2008 23:35:04 GMT

This release contains the SQL Server 2008 RC0 product samples for Reporting Services.

Updated Wiki: SS2008!AdventureWorks Sample Model

bonniefe — Tue, 10 Jun 2008 23:17:46 GMT

Report Model Samples

6/10/2008 1:32:27 AM

With SQL Server Reporting Services, you can build semantic models based on SQL Server databases or Oracle databases running version 9.2.0.3 or later by running Report Model Designer within Business Intelligence Development Studio. After you deploy the model to the report server, you can assign role-based security permissions. Then, your Report Builder users can use the model to build ad hoc reports in Report Builder.

Important:
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

The samples are installed by default at:
<drive>:\Program Files\Microsoft SQL Server\100\Samples
Note Business Intelligence (BI) Development Studio is not supported on Itanium-based computers. However, support for BI Development Studio is available for x64-based computers. If the SQL Server sample databases have been deployed on an Itanium-based computer, use BI Development Studio on either an x86-based or x64-based computer to modify and run the samples.

Scenario

The purpose of this sample is to show SQL Server Reporting Services Model Designer/Report Builder users how report models are structured and how report models are used in Report Builder.

Languages

Semantic Model Definition Language (SMDL)

Features

The AdventureWorks model report sample uses the following features of Reporting Services.

Application Area	Features
Reporting Services	Model Designer
Reporting Services	Report Builder
Reporting Services	Report Manager

Prerequisites

Before running this sample, make sure the following software is installed:

SQL Server, including the following components:
Reporting Services
Business Intelligence Development Studio
One sample database: AdventureWorks (data warehouse)
Microsoft .NET Framework 2.0 on the computer(s) that you are using to run Model Designer and Report Builder.
Visual Studio. In addition, make sure that you have permissions to:

Retrieve data from the AdventureWorks database.
Publish to the report server.
Assign role-based security permissions to catalog items.

Opening the AdventureWorks Model

The sample needs to be deployed to a report server. Place the model files in a network location that is accessible to the computer that you intend to run Model Designer on. After it is deployed, you can open the model in the Business Intelligence Development Studio.

To open the AdventureWorks model in Model Designer

Click Start, point to All Programs, point to Microsoft SQL Server 2008 and then click Business Intelligence Development Studio.
On the File menu, point to Open, and then click Project/Solution.
In Open Project, navigate to the network location where you saved the model files.
Select the Adventure Works Model.sln file, and then click Open.

Note:
Alternatively, you can add the .smdl file to an already existing model by right-clicking the Report Models folder, pointing to Add, and clicking Existing Item. Navigate to the location where you saved the sample files. Select the .smdl file and then click Add.

The sample model is displayed in the Business Intelligence Development Studio window. You can edit the model and .dsv files, save the model to the report server and assign security permissions.

Deploying the Model

When you are finished modifying the model, you need to deploy the model to the report server.

To deploy the AdventureWorks model from Model Designer

In Solution Explorer, right-click the Adventure Works Model project.
On the Build menu, click Deploy Report Model Project.

Note:
Alternatively, right-click the report model project and select Deploy.

Deployment can take several minutes. If successful, a message is displayed at the bottom of the window indicating the model was successfully deployed. If an error occurred during deployment, a message is displayed indicating the error.

Assigning Permissions to the Model

To assign permissions to the AdventureWorks model in Object Explorer

Click Start, point to All Programs, point to Microsoft SQL Server 2008 and then click SQL Server Management Studio.
When prompted, connect to the server where the report model is located.
In Object Explorer, navigate to the model, right-click the model, and click Properties.
In the Model Properties page, click Model Security.
Select the Secure individual model items independently of this model check box.
Click Use these roles for each group or user account.
Click Add Group or User.
Select the group or user for which you are creating the role assignment and then click OK.

Opening the AdventureWorks Model Sample in Report Builder

After you have saved the report model to the report server and assigned the appropriate permissions to the report, you can open it in Report Builder and create reports.

To open the Adventure Works model sample in Report Builder

In your Web browser, type the URL for your report server in the address bar. By default, the URL is http://<webservername>/reports.
Click Report Builder.
In the Getting Started pane, select AdventureWorks, and then click OK.Your model is displayed in the Explorer pane.

Updated Wiki: SS2005!AdventureWorks Sample Model

bonniefe — Tue, 10 Jun 2008 23:17:18 GMT

Report Model Samples

6/10/2008 3:14:30 PM

Updated: 14 April 2006
With SQL Server 2005 Reporting Services, you can build semantic models based on SQL Server databases by running Report Model Designer within Business Intelligence Development Studio. After you deploy the model to the report server, you can assign role-based security permissions. Then, your Report Builder users can use the model to build ad hoc reports in Report Builder.
The AdventureWorks sample report model is shipped with SQL Server 2005. The samples are not installed automatically during setup. For instructions about how to install the samples, see Installing Samples in SQL Server 2005 Books Online.
The samples are installed by default at:
<drive>:\Program Files\Microsoft SQL Server\90\Samples
Note Business Intelligence (BI) Development Studio is not supported on Itanium-based computers. However, support for BI Development Studio is available for x64-based computers. If the SQL Server sample databases have been deployed on an Itanium-based computer, use BI Development Studio on either an x86-based or x64-based computer to modify and run the samples.

Scenario

The purpose of this sample is to show SQL Server Reporting Services Model Designer/Report Builder users how report models are structured and how report models are used in Report Builder.

Languages

Semantic Model Definition Language (SMDL)

Features

The AdventureWorks model report sample uses the following features of Reporting Services.

Application Area	Features
Reporting Services	Model Designer
Reporting Services	Report Builder
Reporting Services	Report Manager

Prerequisites

Before running this sample, make sure the following software is installed:

SQL Server 2005, including the following components:
Reporting Services
SQL Server Management Studio
Business Intelligence Development Studio
One sample database: AdventureWorks (data warehouse)
Microsoft .NET Framework 2.0 on the computer(s) that you are using to run Model Designer and Report Builder.
Visual Studio 2005. In addition, make sure that you have permissions to:

Retrieve data from the AdventureWorks database.
Publish to the report server.
Assign role-based security permissions to catalog items.

Opening the AdventureWorks Model

To open the AdventureWorks model in Model Designer

Click Start, point to All Programs, point to SQL Server 2005 and then click Business Intelligence Development Studio.
On the File menu, point to Open, and then click Project/Solution.
In Open Project, navigate to the network location where you saved the model files.
Select the Adventure Works Model.sln file, and then click Open.

Note:
Alternatively, you can add the .smdl file to an already existing model by right-clicking the Report Models folder, pointing to Add, and clicking Existing Item. Navigate to the location where you saved the sample files. Select the .smdl file and then click Add.

The sample model is displayed in the Business Intelligence Development Studio window. You can edit the model and .dsv files, save the model to the report server and assign security permissions.

Deploying the Model

When you are finished modifying the model, you need to deploy the model to the report server.

To deploy the AdventureWorks model from Model Designer

In Solution Explorer, right-click the Adventure Works Model project.
On the Build menu, click Deploy Report Model Project.

Note:
Alternatively, right-click the report model project and select Deploy.

Assigning Permissions to the Model

To assign permissions to the AdventureWorks model in Object Explorer

Click Start, point to All Programs, point to SQL Server 2005 and then click SQL Server Management Studio.
When prompted, connect to the server where the report model is located.
In Object Explorer, navigate to the model, right-click the model, and click Properties.
In the Model Properties page, click Model Security.
Select the Secure individual model items independently of this model check box.
Click Use these roles for each group or user account.
Click Add Group or User.
Select the group or user for which you are creating the role assignment and then click OK.

Opening the AdventureWorks Model Sample in Report Builder

After you have saved the report model to the report server and assigned the appropriate permissions to the report, you can open it in Report Builder and create reports.

To open the Adventure Works model sample in Report Builder

In your Web browser, type the URL for your report server in the address bar. By default, the URL is http://<webservername>/reports.
Click Report Builder.
In the Getting Started pane, select AdventureWorks, and then click OK.Your model is displayed in the Explorer pane.

Updated Wiki: SS2008!Script Samples (Reporting Services)

bonniefe — Tue, 10 Jun 2008 23:16:38 GMT

Script Samples (Reporting Services)

6/10/2008 1:32:27 AM

The following samples represent scripts written for Reporting Services using Microsoft Visual Basic .NET. Script samples typically address a single feature or technology and are task-based. You can use script files with the Reporting Services SOAP API to access most of the management and administration operations available on your report server.

Important:
Samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator. Microsoft does not provide technical support for these samples.

Important:

Samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator. Microsoft does not provide technical support for these samples.

The following table describes the sample scripts.

File	Description
AddItemSecurity.rss	Demonstrates how to use a script to set item security policies in the report server namespace.
CancelRunningJobs.rss	Demonstrates a sample administration script that cancels jobs that are running on a report server.
ConfigureSystemProperties.rss	Demonstrates a script that can be used to set system-level, report server properties.
PublishSampleReports.rss	Demonstrates a script that publishes the sample reports to a report server.

Requirements

Before you run sample scripts, the following conditions must be met:

The sample reports and the script files must first be installed to your hard drive using Reporting Services Setup or the separate sample installer.
You must have permission to run the rs utility from the computer on which a report server instance is installed.
You must have access to the report server that you are accessing with your script.
You must have appropriate permissions on the root folder of the report server you are accessing. For more information about permissions and user roles, see Granting Permissions on a Native Mode Report Server.

Location of the Script Files

When you install the samples to the default installation directory, scripting samples are located by default in C:\Program Files\Microsoft SQL Server\100\Samples\Reporting Services\Script Samples.

Important:
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Running the Sample Scripts

You can run the sample scripts in the Reporting Services script environment.

To run this sample

Open a command prompt: On the Start menu, click Run, type cmd in the text box, and then click OK.
Navigate to the directory that contains your sample script. For example, if your sample script is installed in the default directory, type the following at the command prompt: * cd C:\Program Files\Microsoft SQL Server\100\Samples\Reporting Services\Script Samples *
At the command prompt, enter the following to see a list of command prompt options available for use with the rs utility: * rs -? * Note: If you receive a message that rs is not a recognized command or batch file, you may need to add the location of rs.exe to your Windows environment variable PATH.
At the command prompt, type the appropriate command to run the sample script file. For example, to run PublishSampleReports.rss type the following command, while replacing the given server URL with the report server you are accessing: * rs -i PublishSampleReports.rss -s http://<Server Name>/reportserver *

Modifying the Script File

You can open any of the .rss files using a text editor.

Updated Wiki: SS2005!Script Samples (Reporting Services)

bonniefe — Tue, 10 Jun 2008 23:16:07 GMT

Script Samples (Reporting Services)

6/10/2008 3:14:30 PM

The following samples represent scripts written for Reporting Services using Microsoft Visual Basic .NET. Script samples typically address a single feature or technology and are task-based. You can use script files with the Reporting Services SOAP API to access most of the management and administration operations available on your report server.

Important:
These samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples.

The following table describes the sample scripts.

File	Description
AddItemSecurity.rss	Demonstrates how to use a script to set item security policies in the report server namespace.
CancelRunningJobs.rss	Demonstrates a sample administration script that cancels jobs that are running on a report server.
ConfigureSystemProperties.rss	Demonstrates a script that can be used to set system-level, report server properties.
PublishSampleReports.rss	Demonstrates a script that publishes the sample reports to a report server.

Requirements

Before you run sample scripts, the following conditions must be met:

The sample reports and the script files must first be installed to your hard drive using Reporting Services Setup or the separate sample installer.
You must have permission to run the rs utility from the computer on which a report server instance is installed.
You must have access to the report server that you are accessing with your script.
You must have appropriate permissions on the root folder of the report server you are accessing. For more information about permissions and user roles, see Managing Permissions and Security for Reporting Services.

Location of the Script Files

When you install the samples to the default installation directory, scripting samples are located by default in C:\Program Files\Microsoft SQL Server\90\Samples\Reporting Services\Script Samples.

Note:
If the samples have not been installed, see Installing Samples.

Running the Sample Scripts

You can run the sample scripts in the Reporting Services script environment.

To run this sample

Open a command prompt: On the Start menu, click Run, type cmd in the text box, and then click OK.
Navigate to the directory that contains your sample script. For example, if your sample script is installed in the default directory, type the following at the command prompt: * cd C:\Program Files\Microsoft SQL Server\90\Samples\Reporting Services\Script Samples *
At the command prompt, enter the following to see a list of command prompt options available for use with the rs utility: * rs -? * Note: If you receive a message that rs is not a recognized command or batch file, you may need to add the location of rs.exe to your Windows environment variable PATH.
At the command prompt, type the appropriate command to run the sample script file. For example, to run PublishSampleReports.rss type the following command, while replacing the given server URL with the report server you are accessing: * rs -i PublishSampleReports.rss -s http://myserver/reportserver *

Modifying the Script File

You can open any of the .rss files using a text editor.

Updated Wiki: SS2008!RSExplorer Sample Application

bonniefe — Tue, 10 Jun 2008 23:15:25 GMT

Readme_RSExplorer Sample Application

6/10/2008 1:32:27 AM

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
RSExplorer is a sample Microsoft Windows application developed in Microsoft Visual C# using Microsoft Visual Studio. The application is based on a real-world scenario, and it demonstrates how to develop a Windows application that uses the Reporting Services Web service. RSExplorer uses a Microsoft .NET Framework proxy class to call Web service methods exposed by the Reporting Services SOAP API. It also highlights new features in the area of enterprise reporting. This sample is not supported on Itanium-based operating systems.

Important:
Sample applications should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

You should be familiar with Visual Studio and Visual Basic or C#, and you should have installed the following to use the RSExplorer sample:

Microsoft Visual Studio 2005. This sample is not compatible with Visual Studio 2008.
SQL Server, including Reporting Services.
Microsoft .NET Framework 2.0.
Reporting Services samples. You can choose to install the samples during SQL Server setup. For this release, when you choose to install samples, a separate installer is installed on your computer that you can launch to extract and install samples. You can run this installer from the Start menu in the Microsoft SQL Server program group.
A report server that you have permission to access on your network, if you plan to use the sample client application to view the contents of a report server and render reports.

Note:
RSExplorer may be converted to compile and run in previous versions of Visual Studio. However, it is designed specifically to be compatible with the version mentioned in this section.

Important:
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Location

This sample is located by default at:
C:\Program Files\Microsoft SQL Server\100\Samples\Reporting Services\Application Samples\ReportSearch Sample

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build and run the RSExplorer sample within Visual Studio

Open the solution (RSExplorerCS.sln or RSExplorerVB.sln).
From the Debug menu, click Start Without Debugging.
To exit the application, choose File and then Exit.

To build and run the RSExplorer sample from the Command Line

Use the Change Directory command to change to the RSExplorer directory.
Type the following to build both the C# and Visual Basic versions of the sample: * for /r %f in (*.sln) do C:\WINDOWS\Microsoft.NET\Framework\v2.0.40607\msbuild.exe "%f" * Note: The Windows system path and .NET Framework version number may differ on your system.
In the application's \Bin\Debug directory, double-click RSExplorer.exe to start the application.
From the File menu, choose Exit to close the application.

Using RSExplorer

After installing the RSExplorer sample application, you can use the sample to view the contents of a report server, add new folders, import reports, edit item properties, and view reports.

Important:
Sample applications should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

To start the RSExplorer sample application

Open RSExplorer.sln in Visual Studio.
On the Debug menu, click Start to run the sample application.
In the Server Address box, enter the virtual root of the report server you want to access for example, http://<localhost>/reportserver, and then click Go. A detailed list of report server items should appear in the Catalog Explorer list view.
Navigate the report server database tree by clicking on folders. You can navigate back by clicking the Up arrow on the toolbar.
Click on any report in the list and click the Show Properties link to view the description and path properties.

To add a folder to the report server database

Navigate to a location in the tree to which you want to add a new folder.
On the File menu, click New, and then click Folder. The Add Folder dialog box opens.
Choose a name and description for the folder, and then click Add.

To import a report

On the File menu, click Import Report. The Import Report File dialog box opens.
Use the dialog box to browse for a Report Definition Language (RDL) file that you want to upload to your report server, and then click Open.

To delete an item from the report server database

Browse to and select an item that you want to delete in the Catalog Explorer list.
On the Edit menu, click Delete. Click Yes to confirm the action.

To copy items in the report server database

Select the item that you want to copy. RSExplorer is limited to copying reports, resources, and data sources.
On the Edit menu, click Copy.
Browse to a folder into which you want to copy the selected item or items, and then, on the Edit menu, click Paste.

To view the properties of a selected item

Select an item in the Catalog Explorer list.
Click the Show Properties link above the right window pane. The properties are displayed.

Updated Wiki: SS2005!RSExplorer Sample Application

bonniefe — Tue, 10 Jun 2008 23:14:52 GMT

RSExplorer Sample Application

6/10/2008 3:14:30 PM

Updated: 5 December 2005
RSExplorer is a sample Microsoft Windows application developed in Microsoft Visual C# using Microsoft Visual Studio. The application is based on a real-world scenario, and it demonstrates how to develop a Windows application that uses the Reporting Services Web service. RSExplorer uses a Microsoft .NET Framework proxy class to call Web service methods exposed by the Reporting Services SOAP API. It also highlights new features in the area of enterprise reporting. This sample is not supported on Itanium-based operating systems.
The SQL Server samples are not installed automatically during setup. For instructions about how to install the samples, see Installing Samples.

Important:
Sample applications should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

You should be familiar with Visual Studio and Visual Basic or C#, and you should have installed the following to use the RSExplorer sample:

Microsoft Visual Studio 2005 or compatible development environment (for viewing the project files).
SQL Server 2005, including Reporting Services.
Microsoft .NET Framework version 2.0.
Reporting Services samples. You can choose to install the samples during SQL Server 2005 setup. For this release, when you choose to install samples, a separate installer is installed on your computer that you can launch to extract and install samples. You can run this installer from the Start menu in the Microsoft SQL Server 2005 program group.
A report server that you have permission to access on your network, if you plan to use the sample client application to view the contents of a report server and render reports.

Note:
RSExplorer may be converted to compile and run in previous versions of Visual Studio. However, it is designed specifically to be compatible with the version mentioned in this section.

Location

This sample is located in the Application Samples\RSExplorer Sample subdirectory of the Reporting Services samples directory.
For example:
C:\Program Files\Microsoft SQL Server\90\Samples\Reporting Services\Application Samples\RSExplorer Sample

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build and run the RSExplorer sample within Visual Studio

Open the solution (RSExplorerCS.sln or RSExplorerVB.sln).
From the Debug menu, click Start Without Debugging.
To exit the application, choose File and then Exit.

To build and run the RSExplorer sample from the Command Line

Use the Change Directory command to change to the RSExplorer directory.
Type the following to build both the C# and Visual Basic versions of the sample: * for /r %f in (*.sln) do C:\WINDOWS\Microsoft.NET\Framework\v2.0.40607\msbuild.exe "%f" * Note: The Windows system path and .NET Framework version number may differ on your system.
In the application's \Bin\Debug directory, double-click RSExplorer.exe to start the application.
From the File menu, choose Exit to close the application.

Using RSExplorer

After installing the RSExplorer sample application, you can use the sample to view the contents of a report server, add new folders, import reports, edit item properties, and view reports.

Important:
Sample applications should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

To start the RSExplorer sample application

Open RSExplorer.sln in Visual Studio.
On the Debug menu, click Start to run the sample application.
In the Server Address box, enter the virtual root of the report server you want to access for example, http://<localhost>/reportserver, and then click Go. A detailed list of report server items should appear in the Catalog Explorer list view.
Navigate the report server database tree by clicking on folders. You can navigate back by clicking the Up arrow on the toolbar.
Click on any report in the list and click the Show Properties link to view the description and path properties.

To add a folder to the report server database

Navigate to a location in the tree to which you want to add a new folder.
On the File menu, click New, and then click Folder. The Add Folder dialog box opens.
Choose a name and description for the folder, and then click Add.

To import a report

On the File menu, click Import Report. The Import Report File dialog box opens.
Use the dialog box to browse for a Report Definition Language (RDL) file that you want to upload to your report server, and then click Open.

To delete an item from the report server database

Browse to and select an item that you want to delete in the Catalog Explorer list.
On the Edit menu, click Delete. Click Yes to confirm the action.

To copy items in the report server database

Select the item that you want to copy. RSExplorer is limited to copying reports, resources, and data sources.
On the Edit menu, click Copy.
Browse to a folder into which you want to copy the selected item or items, and then, on the Edit menu, click Paste.

To view the properties of a selected item

Select an item in the Catalog Explorer list.
Click the Show Properties link above the right window pane. The properties are displayed.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2005!Readme_ReportSearch

bonniefe — Tue, 10 Jun 2008 23:13:10 GMT

ReportSearch in Office Sample Application

6/10/2008 3:14:30 PM

New: 5 December 2005
This sample demonstrates how to integrate SQL Server 2005 Reporting Services into Microsoft Office 2003 using the Research Task pane. You can search and browse report server database items without leaving Office 2003.
The Research Task pane in Office 2003 allows developers to create their own research services. For example, if you have Reporting Services reports stored on a report server and you want to provide those reports to your internal users, you can develop a service using the Research Task pane that functions within Office applications, allowing your Office users to easily access reports while working on Office documents.
The ReportSearch sample shows how a Reporting Services report server database items can be exposed directly within an Office 2003 Research Task pane. The user can browse folders and reports and search for reports while using most Office 2003 applications. For instance, while writing an e-mail, a user can browse to a relevant Reporting Services report in Report Manager. The application is based on a real-world scenario and it demonstrates how to extend the reach of your reports.

Important:
These samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples.

Requirements

You should be familiar with Visual Studio and either C# or Visual Basic, and your system must have installed the following applications to use the ReportSearch sample:

Visual Studio 2005 or compatible development environment (for viewing the project files).
SQL Server 2005, including Reporting Services.
Microsoft Office 2003.
Microsoft .NET Framework version 2.0. You can obtain the .NET Framework SDK free of charge. See Installing the .NET Framework SDK
Reporting Services samples. You can choose to install the samples during SQL Server 2005 setup. For this release, when you choose to install samples, a separate installer is installed on your computer that you can launch to extract and install samples. You can run this installer from the Start menu in the Microsoft SQL Server 2005 program group. For more information, see Installing Samples.
A report server that you have permission to access on your network, if you plan to use the sample client application to view the contents of a report server.
Two sample databases: AdventureWorksDW (data warehouse) and AdventureWorksAS (OLAP).

Location

This sample is located by default at:
C:\Program Files\Microsoft SQL Server\90\Samples\ Reporting Services\Application Samples\ReportSearch Sample
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.

Setting Up the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

In order to build and run this sample, the following steps need to be performed. The sample is designed and tested to run on a single machine.
Authentication and Identity Impersonation is set in web.config. The sample uses Windows Authentication. When possible, use Windows Authentication.
.

To set up the Office research service

Create an Internet Information Services (IIS) vroot folder from the default sample language folder and name it “ReportSearch”. The language folder is \cs for the C# version or \vb for the Visual Basic version.
Enable Integrated Windows Authentication and disable Anonymous access on the ReportSearch vroot folder.
Open one of the Office 2003 applications, such as Microsoft Word 2003.
Click the View menu, and click Task Pane. In the Task pane, click the drop-down arrow and select Research.
Click Research options at the bottom of the Task pane. The Research Options dialog box appears.
Select Add Services.
In the Address box, type http://localhost/ReportSearch/reg.asmx.
Click Add.
Click Continue.
Click Install.

Running the Sample

To view a report in Word 2003

Open Word if it is not open already and open the Research task pane.
In the Search for drop-down list, select Microsoft Reporting Services Sample and press Enter or click the Go button.
Type a folder path or a report name to view catalog items within the task pane. Examples:
Type a forward slash (/) to render all folders and reports within the root folder.
Type any search term to return all folders and reports in any folder with the search term. For example, type “sales” to return all reports and folders containing the word “sales”.
Once folders and/or reports are rendered in the task pane, click a folder to browse to a report summary or a report link to browse to a report within Report Manager. Note: Typing a question mark (?) in the Search for text box will display the Advanced Search Page to search within a specific folder, name, or description field.

Viewing the Sample

To view the sample code

Navigate to the ReportSearch Sample language folder. The language folder is \cs for the C# version or \vb for the Visual Basic version.
Click Open.

Updated Wiki: SS2008!FindRenderSave Sample Windows Application

bonniefe — Tue, 10 Jun 2008 23:12:41 GMT

Readme_FindRenderSave Sample Windows Application

6/10/2008 1:32:27 AM

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
FindRenderSave is a sample Microsoft Windows application developed using Microsoft Visual Studio. The application is based on a real-world scenario, and it demonstrates how to develop a Windows application that uses the Report Server Web service. The sample uses the SOAP API to enable you to search for reports in the report server database, to review the report properties and to render the reports to various on-disk formats. This sample is not supported on Itanium-based operating systems.

Important:
Sample applications should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

You should be familiar with Microsoft Visual Studio and either Microsoft Visual C# or Microsoft Visual Basic, and your system must meet the following requirements to use the FindRenderSave sample:

Visual Studio 2005. This sample is not compatible with Visual Studio 2008.
Microsoft .NET Framework 2.0.
Reporting Services samples.
A report server that you have permission to access on your network, if you plan to use the sample client application to view the contents of a report server and render reports. The sample assumes that you have SQL Server Reporting Services installed on your development computer.

Important:
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Location

This sample is located by default at:
C:\Program Files\Microsoft SQL Server\100\Samples\Reporting Services\Application Samples\FindRenderSave Sample

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build and run the FindRenderSave sample within Visual Studio

Open the solution (FindRenderSaveCS.sln or FindRenderSaveVB.sln).
From the Debug menu, click Start Without Debugging.
To exit the application, click Close.

To build and run the FindRenderSave sample from the Command Line

Use the Change Directory command (CD) to change to the \FindRenderSave directory.
Type the following to build both the C# and Visual Basic versions of the sample: * for /r %f in (*.sln) do C:\WINDOWS\Microsoft.NET\Framework\v2.0.40607\msbuild.exe "%f" * Note: The Windows system path and .NET Framework version number may differ on your system.
In the application's \Bin\Debug directory, double-click FindRenderSave.exe to start the application.
Click Close, to close the application.

Using FindRenderSave

After installing the FindRenderSave sample application, you can use the sample to search for reports, view report properties, and render reports to various on-disk formats. By default, the application attempts to connect to an instance of the Report Server Web service located on the same computer running FindRenderSave.

Important:
Sample applications should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

To use the FindRenderSave sample application

Open FindRenderSave.sln in Visual Studio.
On the Debug menu, click Start to run the sample application.
Use the Search by list to search for reports by name, by description, or by both name and description.
Enter the text that you want to use in your search in the Search string box. When you have finished entering your search string, click Search. A list of reports that match the search criteria appears in the Items found list.
Click on any report in the Items found list to view the description and path properties.
When a report is selected, you can render the report to one of four render formats: Excel, Image, Web archive (MHTML), or PDF. To select a render format, use the Render as list.
To save the report, click Save Report. The Save As dialog box opens. Note: FindRenderSave will not render or save reports requiring credentials or parameterized reports that do not have default values specified for all parameters.
Choose a location and type a name for the report, and then click Save.
To exit the application, click Close.

Updated Wiki: SS2005!FindRenderSave Sample Windows Application

bonniefe — Tue, 10 Jun 2008 23:11:57 GMT

FindRenderSave Sample Windows Application

6/10/2008 3:14:30 PM

Updated: 5 December 2005
FindRenderSave is a sample Microsoft Windows application developed using Microsoft Visual Studio. The application is based on a real-world scenario, and it demonstrates how to develop a Windows application that uses the Report Server Web service. The sample uses the SOAP API to enable you to search for reports in the report server database, to review the report properties and to render the reports to various on-disk formats. This sample is not supported on Itanium-based operating systems.
The SQL Server samples are not installed automatically during setup. For instructions about how to install the samples, see Installing Samples.

Important:
Sample applications should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

You should be familiar with Microsoft Visual Studio and either Microsoft Visual C# or Microsoft Visual Basic, and your system must meet the following requirements to use the FindRenderSave sample:

Visual Studio 2005 or compatible development environment (for viewing the project files).
Microsoft .NET Framework version 2.0.
Reporting Services samples. You can choose to install the samples during SQL Server 2005 setup. For this release, when you choose to install samples, a separate installer is installed on your computer that you can launch to extract and install samples. You can run this installer from the Start menu in the Microsoft SQL Server 2005 program group.
A report server that you have permission to access on your network, if you plan to use the sample client application to view the contents of a report server and render reports. The sample assumes that you have SQL Server 2005 Reporting Services installed on your development computer.

Location

This sample is located in the Application Samples\FindRenderSave Sample subdirectory of the Reporting Services samples directory.
For example:
C:\Program Files\Microsoft SQL Server\90\Samples\Reporting Services\Application Samples\FindRenderSave Sample

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build and run the FindRenderSave sample within Visual Studio

Open the solution (FindRenderSaveCS.sln or FindRenderSaveVB.sln).
From the Debug menu, click Start Without Debugging.
To exit the application, click Close.

To build and run the FindRenderSave sample from the Command Line

Use the Change Directory command (CD) to change to the \FindRenderSave directory.
Type the following to build both the C# and Visual Basic versions of the sample: * for /r %f in (*.sln) do C:\WINDOWS\Microsoft.NET\Framework\v2.0.40607\msbuild.exe "%f" * Note: The Windows system path and .NET Framework version number may differ on your system.
In the application's \Bin\Debug directory, double-click FindRenderSave.exe to start the application.
Click Close, to close the application.

Using FindRenderSave

Important:
Sample applications should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

To use the FindRenderSave sample application

Open FindRenderSave.sln in Visual Studio.
On the Debug menu, click Start to run the sample application.
Use the Search by list to search for reports by name, by description, or by both name and description.
Enter the text that you want to use in your search in the Search string box. When you have finished entering your search string, click Search. A list of reports that match the search criteria appears in the Items found list.
Click on any report in the Items found list to view the description and path properties.
When a report is selected, you can render the report to one of four render formats: Excel, Image, Web archive (MHTML), or PDF. To select a render format, use the Render as list.
To save the report, click Save Report. The Save As dialog box opens. Note: FindRenderSave will not render or save reports requiring credentials or parameterized reports that do not have default values specified for all parameters.
Choose a location and type a name for the report, and then click Save.
To exit the application, click Close.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2008!AsynchronousRender Sample Windows Application

bonniefe — Tue, 10 Jun 2008 23:11:23 GMT

Readme_AsynchronousRender Sample Windows Application

6/10/2008 1:32:27 AM

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
AsynchronousRender is a sample Windows application developed using Visual Studio 2005. The application is based on a real-world scenario, and it demonstrates how to develop a Windows application that uses the Report Server Web service. The sample uses the SOAP API to enable you to view the contents of a local report server, to select a report, and then to render that report to disk using asynchronous server communication. This sample is not supported on Itanium-based operating systems.

Important:
These Samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator. Microsoft does not provide technical support for these samples.

Important:

These Samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator. Microsoft does not provide technical support for these samples.

Requirements

You should be familiar with Visual Studio and one or more of the .NET Framework programming languages, and you should have installed the following to use the AsynchronousRender sample:

Microsoft Visual Studio 2005. This sample is not compatible with Visual Studio 2008.
Microsoft .NET Framework 2.0.
SQL Server, including Reporting Services.
Reporting Services samples.
A report server that you have permission to access on your network, if you plan to use the sample client application to view the contents of a report server and render reports.

Important:
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Location

This sample is located by default at:
C:\Program Files\Microsoft SQL Server\100\Samples\Reporting Services\Application Samples\ReportSearch Sample

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build and run the AsynchronousRender sample within Visual Studio

Open the solution (AsynchronousRenderCS.sln or AsynchronousRenderVB.sln).
From the Debug menu, click Start Without Debugging.
To exit the application, click Exit.

To build and run the AsynchronousRender sample from the Command Line

Use the Change Directory command to change to the AsynchronousRender directory.
Type the following to build both the C# and Visual Basic versions of the sample, modifying the .NET Framework path as appropriate. For example: * for /r %f in (*.sln) do C:\WINDOWS\Microsoft.NET\Framework\v2.0.40607\msbuild.exe "%f" *
In the application's \Bin\Debug directory, double-click AsynchronousRender.exe to start the application.
To exit the application, click Exit.

Using the Sample

After building and running the AsynchronousRender sample application, you can use the sample to browse for and render reports in your report server database. By default, the application attempts to connect to an instance of the Report Server Web Service located on the same computer running AsynchronousRender.

Important:
Sample applications should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

To use the AnynchronousRender sample application

Use the Connect button to make a connection to the local report server and retrieve a list of items in the report server namespace.
Select a report using the TreeView control.
When a report is selected, you can render the report to Web archive (MHTML) asynchronously. To render the report, click Render.An execution timer runs while the application waits for a response from the server. When the report is rendered and ready, a message box appears. To save the report to disk, click Yes.
Choose a location and type a name for the report, and then click Save.
To exit the application, click Exit.

Updated Wiki: SS2005!AsynchronousRender Sample Windows Application

bonniefe — Tue, 10 Jun 2008 23:10:57 GMT

AsynchronousRender Sample Windows Application

6/10/2008 3:14:30 PM

Updated: 5 December 2005
AsynchronousRender is a sample Windows application developed using Visual Studio 2005. The application is based on a real-world scenario, and it demonstrates how to develop a Windows application that uses the Report Server Web service. The sample uses the SOAP API to enable you to view the contents of a local report server, to select a report, and then to render that report to disk using asynchronous server communication. This sample is not supported on Itanium-based operating systems.
The SQL Server samples are not installed automatically during setup. For instructions about how to install the samples, see Installing Samples.

Important:
These samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples.

Requirements

You should be familiar with Visual Studio and one or more of the .NET Framework programming languages, and you should have installed the following to use the AsynchronousRender sample:

Microsoft Visual Studio 2005 or compatible development environment (for viewing the project files).
Microsoft .NET Framework version 2.0.
SQL Server 2005, including Reporting Services.
Reporting Services samples. You can choose to install the samples during SQL Server 2005 setup. For this release, when you choose to install samples, a separate installer is installed on your computer that you can launch to extract and install samples. You can run this installer from the Start menu in the Microsoft SQL Server 2005 program group.
A report server that you have permission to access on your network, if you plan to use the sample client application to view the contents of a report server and render reports.

Location

This sample is located in the Application Samples\AsynchronousRender Sample subdirectory of the Reporting Services samples directory.
For example:
C:\Program Files\Microsoft SQL Server\90\Samples
\Reporting Services\Application Samples\AsynchronousRender Sample

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build and run the AsynchronousRender sample within Visual Studio

Open the solution (AsynchronousRenderCS.sln or AsynchronousRenderVB.sln).
From the Debug menu, click Start Without Debugging.
To exit the application, click Exit.

To build and run the AsynchronousRender sample from the Command Line

Use the Change Directory command to change to the AsynchronousRender directory.
Type the following to build both the C# and Visual Basic versions of the sample, modifying the .NET Framework path as appropriate. For example: * for /r %f in (*.sln) do C:\WINDOWS\Microsoft.NET\Framework\v2.0.40607\msbuild.exe "%f" *
In the application's \Bin\Debug directory, double-click AsynchronousRender.exe to start the application.
To exit the application, click Exit.

Using the Sample

Important:
Sample applications should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

To use the AnynchronousRender sample application

Use the Connect button to make a connection to the local report server and retrieve a list of items in the report server namespace.
Select a report using the TreeView control.
When a report is selected, you can render the report to Web archive (MHTML) asynchronously. To render the report, click Render.An execution timer runs while the application waits for a response from the server. When the report is rendered and ready, a message box appears. To save the report to disk, click Yes.
Choose a location and type a name for the report, and then click Save.
To exit the application, click Exit.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Microsoft SQL Server Product Samples: Reporting Services

New Post: Sample Reports still using 2005 DB

New Post: Sample Reports still using 2005 DB

Source code checked in, #11622

Updated Wiki: Home

Application Samples

Extension Samples

Model Samples

Report Samples

Script Samples

UPDATED RELEASE: SQL Server 2008 RC0 (Jun 10, 2008)

RELEASED: SQL Server 2008 RC0 (Jun 10, 2008)

Updated Wiki: SS2008!AdventureWorks Sample Model

Report Model Samples

Scenario

Languages

Features

Prerequisites

Opening the AdventureWorks Model

To open the AdventureWorks model in Model Designer

Deploying the Model

To deploy the AdventureWorks model from Model Designer

Assigning Permissions to the Model

To assign permissions to the AdventureWorks model in Object Explorer

Opening the AdventureWorks Model Sample in Report Builder

To open the Adventure Works model sample in Report Builder

See Also

Tasks

Other Resources

Help and Information

Updated Wiki: SS2005!AdventureWorks Sample Model

Report Model Samples

Scenario

Languages

Features

Prerequisites

Opening the AdventureWorks Model

To open the AdventureWorks model in Model Designer

Deploying the Model

To deploy the AdventureWorks model from Model Designer

Assigning Permissions to the Model

To assign permissions to the AdventureWorks model in Object Explorer

Opening the AdventureWorks Model Sample in Report Builder

To open the Adventure Works model sample in Report Builder

See Also

Tasks

Other Resources

Help and Information

Updated Wiki: SS2008!Script Samples (Reporting Services)

Script Samples (Reporting Services)

Requirements

Location of the Script Files

Running the Sample Scripts

To run this sample

Modifying the Script File

See Also

Tasks

Other Resources

Help and Information

Updated Wiki: SS2005!Script Samples (Reporting Services)

Script Samples (Reporting Services)

Requirements

Location of the Script Files

Running the Sample Scripts

To run this sample

Modifying the Script File

See Also

Tasks

Other Resources

Help and Information

Updated Wiki: SS2008!RSExplorer Sample Application

Readme_RSExplorer Sample Application

Requirements

Location

Building the Sample

To generate a strong name key file

To build and run the RSExplorer sample within Visual Studio

To build and run the RSExplorer sample from the Command Line

Using RSExplorer

To start the RSExplorer sample application