c

Microsoft SQL Server 2005 Integration Services Step by Stepc

cc
c c
Open table as c

cc
spreadsheet 

c
cc
SSIS package A discrete executable unit of work composed of a collection of control flow
and other objects, including data sources, transformations, process sequence,
and rules, error and event handling, and data destinations.
Containers Package objects that provide structure to packages and special services to
tasks. Containers are used to support repeating control flows in packages and
to group tasks. Containers can include other containers in addition to tasks.
Tasks Package elements that define activities and processes, including data sources,
destinations, transformations, and others.
Precedence Constraints that link executables, containers, and tasks within the package
constraints control flow and specify conditions that determine the sequence and
conditions for determining whether executables run.
Variables Storage for values that an SSIS package and its containers, tasks, and event
handlers can use at run time. The scripts in the Script task and the Script
component can also use variables.
Control flow An SSIS package process control component used to control flow elements:
the containers that provide structure in packages and services to tasks, tasks
that provide functionality in packages, and precedence constraints that
connect containers and tasks.
Data flow An SSIS package data process control component defined from within
package control flow that loads data from sources, transforms and routes it
through transformations, and saves it to destinations.
Event handler An SSIS package process control component used to define the process
activities to be performed at the time of a specific event state for the package
or for any of its tasks or containers.
Data Pipeline The memory-based, multithreaded, buffered transformation process flow of
data through an SSIS data flow task during package execution.
BIDS SQL Server Business Intelligence Development Studio. Provides the
Integration Services project in which you create packages, their data sources,
and data source views.
SSMS SQL Server Management Studio. Provides the Integration Services service
that you use to manage packages and monitor running packages.

1|

c
c

cc
c c
Open table as c

cc
spreadsheet 

c
cc
Solution A container for projects in BIDS. It can contain multiple projects, but at a
minimum, a solution contains one project.
Project Contains all of the files and object definitions for a specific type of
business intelligence project (such as Integration Services, Analysis
Services, or Reporting Services). All of these files are managed in a file
system folder and are referenced in the project definition files.
Business A special edition of Visual Studio that is installed with the SQL Server
Intelligence 2005 client tools. No special licensing is required, and it may be distributed
Development freely within the organization for BI and database developers connected to
Studio (BIDS) a database server.
SSIS package Consists of connection managers, control flow tasks, containers, data
sources, transformations, and data destinations. These components are used
in concert to perform data extract, transform, and load (ETL) operations.
SSIS Import and Used to create a package from SQL Server Management Studio (SSMS) or
Export Wizard from an SSIS project in BIDS. A package and all of its components can
also be created manually in an SSIS project within the BIDS environment.
Visual SourceSafe A version control system similar to Microsoft Team Foundation that is used
to manage files and collaborate with other developers. These applications
maintain a central copy of the files and allow files to be checked out,
checked in, and locked by different developers. A project and all related
files should be managed within the developer's personal hard disk or file
system. A single project should never be shared between different
developers. These files should be backed up regularly regardless of whether
they are to be shared with others.
Execute package In BIDS, a package that can be executed in Debug mode by using the
Debug menu or toolbar or from Solution Explorer. In production, the
package can be executed from the command line or from a Microsoft
Windows utility, or it can be scheduled for automated execution by using
the SQL Server Agent.

c

cc
c c
Open table as c

cc
spreadsheet cc

2|

c
c

Open table as c

cc
spreadsheet cc
Create an Integration Start SQL Server Business Intelligence Development Studio. On the File
Services package menu, point to New, and then click Project. Make sure that the Project
Type is set to Business Intelligence Projects, and then click the
Integration Services Project template. Type a name for the project.
Specify the location folder for the project and confirm that the Create
Directory For Solution check box is selected. Click OK.
Add an OLE DB Right-click anywhere in the Connection Managers pane at the bottom of
connection manager the Control Flow tab and click New OLE DB Connection. Click New to
define a new connection. Keep the default: Native OLE DB\SQL Server
Native Client. Type localhost for the Server Name. Select Use Windows
Authentication and choose the desired database.
Review available Right-click anywhere in the Connection Managers pane at the bottom of
connection manager the Control Flow tab and explore the list of connections available: Flat
types File Connection, ADO.NET Connection, Analysis Services Connection,
and so on.
Add an Excel Right-click anywhere in the Connection Managers pane at the bottom of
connection manager the Control Flow tab and click New Connection. In the SSIS connection
manager, click EXCEL (connection manager for Excel files) and click
Add. Type a name for the Excel file and specify an Office Excel file
path.
Create a data flow Click the Data Flow tab. If you go to the Data Flow page right after
task creating a package, you will see a message stating that no data flow tasks
have been added to the package. Click the message link to add a new
task. You can also access it from the Control Flow page.
Add an OLE DB Drag OLE DB Source from the Toolbox to the grid. The small red circle
Source data adapter on this data adapter means that it needs a connection manager.
Add a connection Double-click the OLE DB Source data adapter to open the Editor and
manager to the OLE click OLE DB Connection Manager. In OLE DB Connection Manager,
DB Source data select a connection manager. In the Data Access Mode, select Table Or
adapter View and choose the desired table.
Map the connection Click columns from the left panel of the OLE DB Source Editor. This
manager to the data action maps columns from the connection manager to output columns of
adapter the adapter.
Add an Excel Open the Toolbox and expand Data Flow Destinations. Drag Excel
Destination data Destination from the Toolbox to the grid. The small red circle on this
adapter data adapter means that it needs a connection manager.
Add an Excel Double-click the Excel Destination data adapter. This is a destination
connection manager to component that needs to be connected to the input source component.
the Excel Destination Click the OLE DB Source adapter and connect it to the Excel Destination
data adapter adapter by dragging the green arrow from OLE DB Source to Excel
Destination. Double-click the Excel Destination data adapter to open the

r|

c
c

Open table as c

cc
spreadsheet cc
Editor and verify that the connection manager is selected. In the Name
text box of the Excel sheet, click New. Change the name of the sheet and
change the size of long columns. The Excel connection manager will not
allow creation of long columns. Finally, click Mapping in the left panel
of the Editor.
Execute the package Right-click the desired package and choose Execute Package.
Create a data source In Solution Explorer, right-click the Data Sources folder, and then click
New Data Source. On the Welcome To The Data Source Wizard page,
click Next. On the Select How To Define The Connection page, verify
that Create A Data Source Based On An Existing Or New Connection is
selected, and then click New. Leave the Native OLE DB\SQL Native
Client provider selected. Type 
 in the Server Name text box,
select Use Windows Authentication, and select a database. Click OK,
and then click Finish twice.
Create a data source In Solution Explorer, right-click the Data Source Views folder, and then
view click New Data Source View. Click Next on the Welcome To The Data
Source View Wizard page. Select a data source and click Next. Select the
objects you want to include in your data source view. Click next, and
then click Finish.
Create a new Named In Solution Explorer, expand the Data Source Views folder, and then
Query open the data source view. In the Tables pane, right-click an open area,
and then click New Named Query. Type a name for the new named
query and specify a SQL statement in the bottom pane to define your
named query. Click OK.
Add a connection In the Connection Managers pane, right-click an open area, and then
manager from Data click New Connection from Data Source. In Select Data Source, choose a
Source data source that you created.
Set an OLE DB In the designer, drag a Data Flow task from the Control Flow, open the
Source from a Named Data Flow, and drag an OLE DB Source from the Data Flow Sources tab.
Query Double-click the OLE DB Source component. Then, select and expand
the data source you created from the OLE DB connection manager list.
Select the data source view from the tree and click OK. In data access
mode, select Named query and click OK.
c

å|

c