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

» Database Journal Home
» Database Articles
» Database Tutorials
MS SQL
Oracle
DB2
MS Access
MySQL
» RESOURCES
Database Tools
SQL Scripts & Samples
Links
» Database Forum
» Sitemap
Free Newsletters:
DatabaseDaily  
News Via RSS Feed


follow us on Twitter
Database Journal |DBA Support |SQLCourse |SQLCourse2
 

Featured Database Articles

Posted Oct 11, 2006

Procedure: Ascertain Connectivity of the Analysis Services Data Source

By William Pearson

Objective:

Use this procedure to ensure connectivity of a project’s Shared Data Source with an Analysis Services database.

Background:

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, within a data source context, as a server / instance combination, versus a server name alone (the default for the AdventureWorks Sample Reports project sample’s connection is localhost).

From within the open Adventure Works Reports Sample project, in the SQL Server Business Intelligence Development Studio, take the following steps:

  1. Double-click AdventureWorksAS.rds, within the Shared Data Sources folder seen in Solution Explorer.

The Shared Data Source dialog opens, and appears with default settings as depicted in Illustration 1.


Illustration 1: The Shared Data Source Dialog with Default Settings ...

  1. Click the Edit button on the Shared Data Source dialog.

The Connection Properties dialog opens, and appears with default settings shown in Illustration 2.


Illustration 2: The Connection Properties Dialog 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 many of our environments, the requirement 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 as to whether we need to make this change).

  1. If appropriate, type the correct server / instance name into the Server name box of the Connection Properties dialog. (Mine is MOTHER1\MSSQL2K5, as depicted in Illustration 3.)


Illustration 3: The Connection Properties Dialog with Corrected Settings ...

  1. Ensure that authentication settings are correct for the local environment.
  2. Click the Test Connection button.

A message box appears, indicating that the Test connection succeeded, assuming that our changes (or lack of same, as appropriate) are appropriate. The message box appears as shown in Illustration 4.


Illustration 4: Testing Positive for Connectivity ...

  1. Click OK to dismiss the message box.
  2. Click OK to accept changes, as appropriate, and to dismiss the Connection Properties dialog.

The Shared Data Source dialog appears, with our modified settings, similar to that depicted in Illustration 5.


Illustration 5: The Shared Data Source Dialog with Modified Settings ...

  1. Click OK to close the Shared Data Source dialog, and to return to the development environment.


Comment and Contribute

 


(Maximum characters: 1200). You have characters left.

 

 




Latest Forum Threads
DB2 Forum
Topic By Replies Updated
tables get lock during backup in db2 v9.5 Hamsoo 0 May 8th, 01:03 AM
Query to Pull Last 7 days records from a table vgoushik 0 March 20th, 06:05 PM
DB2 Visual studio addin: ANSI/Unicode problem 10Pints 0 October 5th, 02:08 AM
Things that are everbodys labor day ideas? Lipsett197 0 September 1st, 09:42 AM


















Thanks for your registration, follow us on our social networks to keep up-to-date