SQL Server Integration Services: Difference between revisions

Content deleted Content added
m describe a few more features
Line 1:
e'''SQL Server Integration Services''' ('''SSIS''') is a component of [[Microsoft SQL Server]] 2005. It replaces [[Data Transformation Services]], a feature of SQL Server since Version 7.0.
 
Integration Services provides a platform to build data integration and workflow applications. The primary use for SSIS is [[data warehouse|data warehousing]], as the product features a fast and flexible data extraction, transformation, and loading ([[Extract, transform, load|ETL]]) engine. The tool may also be used to automate maintenance of SQL Server databases.
Line 7:
Like DTS, SSIS features a [[Wizard (software)|wizard]] that lets the user readily create a package which moves data from a single data source to a destination with no transformations. This tool is called the '''Import/Export Wizard'''. The Wizard is approprite for use to quickly move data into or out of SQL Server from or to a variety of sources, including text files and other SQL Server instances.
 
SSIS users utilize a visual designer hosted in the Visual Studio shell. This designer is called the SQL Server Business Intelligence allows users to edit '''SSIS packages''' using by a drag-and-drop user interface. The package holds a variety of elements that define the work the package does when executed.
 
'''Connections'''. A connection includes the information necessary to connect to a particular data source. Tasks can reference the connection by its name, allowing the details of the connection to be changed or configured at runtime.
Line 18:
 
'''Variables'''. Tasks may reference variables to store results or make decisions or affect their configuration.
 
A package may be saved to a file or to a store with a heirarchical namesapce within a SQL Server instance. In either case, the package contents is persisted in [[XML]].
 
Once completed, the designer also allows the user to start package's execution. Once started, the package may be readily debugged or monitored.
 
===Features of the data flow task===
The Data Flow task, arguably the most important task in the product, features a different design surface than that of the workflow. Data flows are edited withn the same design tool, of course. The user can draw data sources, transforms, and data destinations connecting them together in order to achieve the transfer and transforms they desire.
 
Data sources can connect to any number of source types using [[OLEDB]] or ADO. They generally execute a SQL statement (including a stored procedure) to retrieve rows, though there are exceptions. Most notably, a flat file data source allows reading from text files, and an XML adapter can source data from XML files. Similarly, data destinations write data to their target by executing a statement on its connection, or writing to a file.
 
Various transforms exist in the product, including a sort, aggregation, and lookup. A derived column transform evaluates an expression to compute the value for a new column. A script transform is available which allows more complicated transform to be written in [[VBScript]].
Line 29 ⟶ 33:
 
Any number of sources or destinations are supported in a data flow.
 
==Other included tools==
 
Aside from the Import/Export Wizard and the designer, the product includes a few other notable tools.
 
DTEXEC executes a package from the command line wherever it may be stored. Before running the package, the tool may be instructed to apply configuration information, which will allow the same package to be reused with slightly different parameters, including different connection strings for its endpoints.
 
DTSUTIL provides the ability to manage packages, again from the [[command prompt]]. The tool can copy or move a package from a file into the server store, or back out again. Among a few other sundry functions, it can be used to delete, rename, encrypt, or decrypt packages.
 
==Extensibility and Programabiltiy==