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 Feb 13, 2006

Process Analysis Services Objects with Integration Services - Page 3

By William Pearson


Add the Analysis Services Processing Task to the Integration Services Package

We need an Integration Services package within our new project before we can add the Analysis Services Processing task (which forms the focus of our lesson). While there are several ways to create a package within the Business Intelligence Development Studio, we will not have to create a package separately, in our present case – SSIS automatically added an empty "starter" package within the project when we created it. It is good to keep in mind, however, that, should we have already had a solution in place, containing an existing package (such as an ETL package) or packages, and we decided to combine the Analysis Services Processing task with the existing package, for reasons similar to those we noted in our introductory comments, we would have to create and add an Integration Services package to the solution before adding our Analysis Services Processing task.

While we are adding a single task to the package for our present purposes, packages typically contain several tasks, with each task set to run within the context of the package control flow. Workflows that run in response to run-time events, called event handlers, can also have tasks. To add functionality to a package, we typically build the control flow and data flows, add connection managers, and implement other Integration Services features that a given package requires. In our present case, the steps involved will be minimal. We will begin by giving the automatically created package a more meaningful name.

1.  Within the Solution Explorer, expand the SSIS Packages folder, if required.

2.  Right-click the Package.dtsx file that appears underneath the folder in the tree.

3.  Select Rename from the context menu that appears, as depicted in Illustration 5.

Illustration 5: Select Rename from the Context Menu ...

4.  Type the following in place of the now-highlighted package name:


NOTE: Be sure to include the .dtsx file extension.

The package appears, with the proposed name, in Solution Explorer, as shown in Illustration 6.

Illustration 6: Renaming the Package in Solution Explorer ...

5.  Click outside the caption box, to "set" the new name.

A message box appears, asking if we wish to rename the package object as well, as depicted in Illustration 7.

Illustration 7: Message Box Asks If We Wish to Rename Package Object, As Well ...

6.  Click OK to rename the package object, too, and to dismiss the message box.

The SSIS Designer opens, defaulted to the Control Flow tab.

7.  Click the Control Flow tab, if it does not already appear, to move to it.

The Control Flow tab bears a message telling us to add objects, and related matters, from the Toolbox, as shown in Illustration 8.

Illustration 8: Control Flow Tab, and Message Regarding Object Addition and Related Matters

We will add the Analysis Services Processing task to the package at this point.

8.  Select View --> Toolbox from the main menu, as depicted in Illustration 9.

Illustration 9: Opening the Toolbox ...

The Toolbox appears. In the upper half, we see Control Flow Items. It is here that we will obtain the Analysis Services Processing task object, one of two Analysis Services objects that appear within the Control Flow Items group atop the Toolbox.

9.  Click and drag the Analysis Services Processing Task item from the Toolbox to the design surface of the Control Flow tab, as shown in Illustration 10.

Illustration 10: Drag the Analysis Services Processing Task to the Control Flow Design Surface

The Analysis Services Processing Task item appears on the design surface as depicted in Illustration 11. We note that a red circle, containing a white "X," appears on the right side of the box. Passing the mouse pointer over the item produces a rollover caption that reads "No connection manager is specified," as depicted in Illustration 11.

Illustration 11: The Task Appears – and Reminds Us to Add a Connection Manager ...

We will add an Analysis Services Connection Manager to the package in the section that follows.

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