Ascertain Connectivity of the Shared Relational Data Source
first ensure we have a working shared data source. Many of us will be
running "side-by-side" installations of MSSQL Server 2000
and MSSQL Server 2005. This means that our installation of the latter
will need to be referenced as a server / instance combination, versus a server
name alone (the default for the Adventure Works DW project sample's
connection is localhost).
Works.ds, within the Data Sources folder seen in Solution
Source Designer opens, defaulted to the General tab, and appears with
default settings as shown in Illustration 10.
Illustration 10: The Data
Source Designer with Default Settings ...
Click the Edit
button on the Data
Source Designer dialog.
Manager opens, and appears with default settings depicted in Illustration
Illustration 11: The
Connection Manager with Default Settings ...
We note that the default Server name is "localhost."
While this might prove an adequate setting for a PC with only MSSQL Server
2005 installed (default instance), in the case of many of our
installations, the requirement here is for the server / instance
combination that correctly identifies the correct MSSQL Server 2005
instance. (Clicking the Test Connection button at this point will
provide confirmation whether we need to make this change).
appropriate, type the correct server / instance name into the Server
name box of the Connection
Manager. (Mine is
MOTHER1\MSSQL2K5, as shown in Illustration 12.)
Illustration 12: The
Connection Manager, with Corrected Settings ...
authentication settings are correct for the local environment.
Click the Test
Manager message box appears, indicating that the Test connection
succeeded, assuming that our changes (or lack of same, as appropriate) are
proper. The message box appears as depicted in Illustration 13.
Illustration 13: Testing
Positive for Connectivity ...
to dismiss the message box.
to accept changes, as appropriate, and to dismiss the Connection Manager.
Source Designer appears, with our modified settings, similar to that shown
in Illustration 14.
Illustration 14: The
Data Source Designer with Modified Settings ...
to close the Data
and to return to the development environment.
Deploy the Analysis Services Project
Before going further, let's deploy our Analysis
Services project to ensure that we are all "in the same place"
with regard to its status. This will ensure issue-free access for Reporting
Services as we progress within our practice preparation and procedures.
the Adventure Works DW Analysis Services project in the Solution
from the context menu that appears, as depicted in Illustration 15.
Illustration 15: Initiating
Analysis Services Project Deployment ...
The Build and Deployment processes get underway, as
we note the Deployment Progress window appears (by default underneath
the Solution Explorer, in the bottom right corner of the development
NOTE: Be sure to properly configure Properties
of the Analysis Services project to ensure that these processes can
occur. For more information on configuration, and guidance for settings in the
local environment, see the appropriate references in the MSSQL Server 2005
The Build and Deployment processes continue, as
each event is logged in the Deployment Progress window. Finally, the
processes complete, and we see the Deployment Completed Successfully
status announced, as shown in Illustration 16.
Illustration 16: Successful
Deployment is Indicated
We are now ready to "clone" a sample report
project and proceed with the practice exercise. To prepare for this, we will
add a new Report Server project to our existing solution.
Add a New Reporting Services Project
in the same manner that we cloned the Adventure Works project, we will
add a copy of an existing Report Server project, together with its
sample reports, primarily to save time in getting to the focus of our session,
working with KPIs within Reporting Services
the Solution 'Adventure Works level, atop the tree within the Solution
--> Existing Project ... from the cascading context menus
that appear, as depicted in Illustration 17.
Illustration 17: Adding a
Project to the Solution ...
Existing Project dialog appears.
the actual location
of the AdventureWorks sample reports.
The reports are installed, by default (and, therefore,
subject to be installed in a different location on our individual machines), in
the following location
C:\Program Files\Microsoft SQL Server\90\Samples\Reporting Services\Report Samples\
the AdventureWorks Sample Reports folder within the Reports Samples
from the context menu that appears, as shown in Illustration 18.
Illustration 18: Copying
the Sample Reports Folder ...
Navigate back into
the RS029 MSAS KPIs in ReportServices folder, which contains the Analysis
Services project clone we created earlier.
the area within the folder, as we did earlier.
from the context menu that appears, as depicted in Illustration 19.
Illustration 19: Pasting
the Sample Folder in the RS029 MSAS KPIs in ReportServices Folder
Sample Reports folder appears, via the Add Existing Project
dialog, in the new location, as shown in Illustration 20.
AdventureWorks Sample Reports Folder in Its New Location ...
Click the AdventureWorks Sample Reports folder to open it.
10. Select the AdventureWorks
Sample Reports.rptproj file that appears, as depicted in Illustration 21.
Illustration 21: Select
the AdventureWorks Sample Reports.rptproj File
Click Open to
add the Report Server project to our solution.
Sample Reports project appears, with associated objects, in Solution
Explorer, as shown in Illustration 22.
Illustration 22: The New
Solution, Project and Objects within the Solution Explorer
have saved many steps with our cloning approach, we still have to ascertain
connectivity with the Analysis Services data source, just as we did with
the relational data source earlier.