Database Journal
MS SQL Oracle DB2 Access MySQL PostgreSQL Sybase PHP SQL Etc SQL Scripts & Samples Tips Database Forum Rss Feed

» Database Journal Home
» Database Articles
» Database Tutorials
MS Access
SQL Scripts & Samples
» Database Forum
» Slideshows
Free Newsletters:

News Via RSS Feed

Rss Feed

Database Journal |DBA Support |SQLCourse |SQLCourse2

Featured Database Articles


Posted Mar 21, 2005

MSSQL Server Reporting Services: Black Belt Administration: "Governor" Capabilities: Report Execution Timeout - Page 5

By William Pearson

Add the Report Data Source

We learned in Managing Reporting Services: Data Connections and Uploads that when we refer to a data source in Reporting Services, we are referring to a collection of properties, in effect, that represents a connection to a given data source. This collection of properties has a name, as it does in other applications where data sources exist (a scenario with which most of us are familiar). Data sources contain the following, where applicable:

  • Specification of the data processing extension we use to process queries of the type for which we intend to use the connection;
  • A connection string that allows us to locate the source;
  • Access credentials involved in allowing us to read the data within the source.

As we have noted in various articles of the series, a data source connection can be embedded in a report (where it is typically defined within the creation process); it can also be defined as a shared data source item that is managed by a Report Server. The data source connection can be created either within the Report Designer in Visual Studio .NET, or at within the Report Manager. In this section, we will "import" the data source to which our sample report clone is already pointed, to make things quick and easy. This way, we can concentrate on Report Execution Timeout settings, the primary focus of the article.

1.  From within the Solution Explorer, right-click the Shared Data Sources folder that appears underneath the new RS015 project we created earlier.

2.  Select Add on the context menu that appears.

3.  Select Add Existing Item from the cascading menu that appears next, as shown in Illustration 8.

Illustration 8: Select Add --> Add Existing Item

The Add Existing Item dialog for the project appears.

4.  Navigate to, and select, the AdventureWorks.rds file that we copied to its new location, as depicted in Illustration 9.

Illustration 9: Select the AdventureWorks Data Source File in the Add Existing Item Dialog

5.  Click Open.

AdventureWorks.rds is added to the folder, as shown in Illustration 10. (The Shared Data Sources folder is expanded in order to see the file.)

Illustration 10: The AdventureWorks.rds File Appears within the Shared Data Sources Folder

All that remains in our preparation phase is to add, test and publish the clone report.

MS SQL Archives

Latest Forum Threads
MS SQL Forum
Topic By Replies Updated
SQL 2005: SSIS: Error using SQL Server credentials poverty 3 August 17th, 07:43 AM
Need help changing table contents nkawtg 1 August 17th, 03:02 AM
SQL Server Memory confifuration bhosalenarayan 2 August 14th, 05:33 AM
SQL Server Primary Key and a Unique Key katty.jonh 2 July 25th, 10:36 AM