Procedure: Ascertain Connectivity of the Relational Data Source
November 9, 2006
Use this procedure to ensure connectivity with a relational 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, within a data source context, as a server / instance combination, versus a server name alone (the default for the Adventure Works DW project samples connection is localhost).
From within the open Analysis Services project, in the SQL Server Business Intelligence Development Studio, take the following steps:
The Data Source Designer opens, defaulted to the General tab, and appears with default settings as shown in Illustration 1.
The Connection Manager opens, and appears with default settings depicted in Illustration 2.
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 as to whether we need to modify Server name).
A Connection 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 4.
The Data Source Designer reappears, with our modified settings, similar to that shown in Illustration 5.