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 Dec 20, 2004

MSSQL Server Reporting Services: Black Belt Components: Ad Hoc Conditional Formatting for OLAP Reports - Page 4

By William Pearson

Modify the FoodMart Sales Report

In this section, we will copy the existing FoodMart Sales report, and then open it in Reporting Services' Report Designer, where we will begin the modifications that the information consumers have requested.

Set up a Data Connection for the FoodMart Sales Report

Our next step is to set up a Data Connection. As we have noted numerous times throughout our series, Reporting Services can connect with, and create the DataSets it needs from virtually any ODBC or OLE DB-compliant data source (in addition to the obvious MSSQL Server and MSAS data stores). .NET-based API's add the potential for other data sources, assuming that you have a legacy, or otherwise "alternative," scenario on your hands.

Let's set up a Connection to support the DataSet within our practice example.

1.  Right-click the Shared Data Sources folder underneath the new RS012 project tree in the Solution Explorer.

2.  Select Add New Data Source from the context menu that appears, as depicted in Illustration 6.

Illustration 6: Select Add New Data Source from the Context Menu

The Data Link Properties dialog appears, defaulted to the Connection tab.

3.  Click the Provider tab, to select it.

4.  Select Microsoft OLE DB Provider for OLAP Services 8.0 from the Provider list box, as shown in Illustration 7.

Illustration 7: Selecting Microsoft OLE DB Provider for OLAP Services 8.0 - Providers Tab

5.  Click Next, to move to the Connection tab.

6.  In the Data Source box, type the name of the server upon which MSAS resides (mine is MOTHER1 in the illustration that follows).

7.  Type in the server name again in the Location box.

8.  Provide the appropriate authentication information to access the MSAS environment on the server you have selected.

I am using Windows NT Integrated Security, as this is not a production environment. For a production environment, selections here require careful consideration.

9.  Select FoodMart 2000 in the list of data sources that appear when we click the down-arrow selector button at the next box (and thus receive confirmation that our server / authentication information is adequate to display the sources) at the top of the Data tab.

The completed Data Link Properties - Connection tab appears as depicted in Illustration 8.

Illustration 8: Data Link Properties - Connection Tab

10.  Click the Test Connection button to confirm connectivity.

The Microsoft Data Link message box appears, indicating a successful test, as shown in Illustration 9.

Illustration 9: Testing Positive for Connectivity ...

11.  Click OK to close the message box.

12.  Click OK to accept the settings we have made, and to close the Data Link Properties dialog.

Having established the data source, we are now ready to create a copy of the FoodMart Sales sample report, which we will then modify to meet the expressed requirements of the information consumers.

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