SQL Server Integration Services

SQL Server Integration Services (SSIS) is a component of the Microsoft SQL Server database software that can be used to perform a broad range of data migration tasks.

SQL Server Integration Services
Developer(s)Microsoft
Operating systemMicrosoft Windows
TypeETL Tools
LicenseProprietary commercial software
Websitetechnet.microsoft.com/en-us/library/ms141026.aspx

SSIS is a platform for data integration and workflow applications. It features a data warehousing tool used for data extraction, transformation, and loading (ETL). The tool may also be used to automate maintenance of SQL Server databases and updates to multidimensional cube data.

First released with Microsoft SQL Server 2005, SSIS replaced Data Transformation Services, which had been a feature of SQL Server since Version 7.0. Unlike DTS, which was included in all versions, SSIS is only available in the "Standard", "Business Intelligence" and "Enterprise" editions.[1] With Microsoft "Visual Studio Dev Essentials" it is now possible to use SSIS with Visual Studio 2017 free of cost so long as it is for development and learning purposes only.

Features

The SSIS Import/Export Wizard lets the user create packages that move data from a single data source to a destination with no transformations. The Wizard can quickly move data from a variety of source types to a variety of destination types, including text files and other SQL Server instances.

Developers tasked with creating or maintaining SSIS packages use a visual development tool based on Microsoft Visual Studio called the SQL Server Business Intelligence Development Studio (BIDS). It allows users to edit SSIS packages using a drag-and-drop user interface. A scripting environment for writing programming code is also available in the tool. A package holds a variety of elements that define a workflow. Upon package execution, the tool provides color-coded real-time monitoring. (Note: In more recent versions MS SQL Server, BIDS has been replaced with "SQL Server Data Tools - Business Intelligence" (SSDT-BI).[2][3])

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 run time.
Event handlers
A workflow can be designed for a number of events in the different scopes where they might occur. In this way, tasks may be executed in response to happenings within the package — such as cleaning up after errors.
Parameters (SQL Server 2012 Integration Services)
Parameters allow you to assign values to properties within packages at the time of package execution. You can have project parameters and package parameters. In general, if you are deploying a package using the package deployment model, you should use configurations instead of parameters.
Precedence constraints
Tasks are linked by precedence constraints. The precedence constraint preceding a particular task must be met before that task executes. The run time supports executing tasks in parallel, if their precedence constraints so allow. Constraints may otherwise allow different paths of execution depending on the success or failure of other tasks. Together with the tasks, precedence constraints comprise the workflow of the package.
Tasks
A task is an atomic work unit that performs some action. There are a couple of dozen tasks that ship in the box, ranging from the file system task (that can copy or move files) to the data transformation task. The data transformation task actually copies data; it implements the ETL features of the product
Variables
Tasks may reference variables to store results, make decisions, or affect their configuration.

A package may be saved to a file or to a store with a hierarchical namespace within a SQL Server instance. In either case, the package content is persisted in XML.

Once completed, the designer also allows the user to start the package's execution. Once started, the package may be readily debugged or monitored.

Features of the data flow task

SSIS provides the following built-in transformations:[4]

AggregationExport & Import ColumnPivot
AuditFor loop ContainerRow Count
Cache Transform[5]Foreach Loop ContainerRow Sampling
Copy/Map(Fuzzy) LookupScript Component
Data ConversionFuzzy GroupingSlowly Changing Dimension
Data Mining Model TrainingOLE DB CommandTerm Extraction
Data Mining QueryPartition ProcessingTerm Lookup
Derived ColumnPercentage Sampling[6]Unpivot
Dimension ProcessingRow Sampling Transformation

The Conditional Split transformation is used to conditionally route rows to other transformation objects based on a particular condition. It is similar to the "if … else" construct in the C language.

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.[7][8] 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.

DTUTIL provides the ability to manage packages from the command prompt.[9][10] 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 programmability

Users may write code to define their own connection objects, log providers, transforms, and tasks.[11][12]

SSIS features a programmable object model that allows developers to write their own hosts for package execution. Such a host can respond to events, start and stop packages, and so on. The object model also allows developers to create, store, and load packages, as well as create, destroy, and modify any of the contained objects.

Within limits, SSIS packages can load and call CLI assembly DLLs, providing access to virtually any kind of operation permissible by the .NET CLR.

SSIS can be used on all SQL Server 2005, 2008, 2008 R2, 2012, 2014 and 2016 editions except Express and Workgroup.

See also

References
  1. "Features Supported by the Editions of SQL Server 2014". msdn.microsoft.com. Microsoft Developer Network. Retrieved 20 August 2014.
  2. http://sqlmag.com/sql-server-2014/q-where-business-intelligence-development-studio-bids-sql-server-2014
  3. http://blogs.msdn.com/b/analysisservices/archive/2013/03/06/sql-server-data-tools-business-intelligence-for-visual-studio-2012-released-online.aspx
  4. "Integration Services Transformations". Microsoft Developer Network. Microsoft. Retrieved 22 March 2013.
  5. "Cache Transform". Microsoft Developer Network. Microsoft. Retrieved 22 March 2013.
  6. "Percentage Sampling Transformation". Microsoft Developer Network. Microsoft. Retrieved 22 March 2013.
  7. "dtexec Utility (SSIS Tool)". Microsoft Developer Network. Microsoft. Retrieved 2013-03-24.
  8. Marcin Policht (2010-08-09). "Executing SSIS Packages Using DTExec". Database Journal. Retrieved 2013-03-24.
  9. "dtutil Utility (SSIS Tool)". Microsoft Developer Network. Microsoft. Retrieved 2013-03-24.
  10. Yan Pan (2008-03-20). "Using dtutil to copy SSIS packages stored in SQL Server". Database Journal. Retrieved 2013-03-24.
  11. "Developing a Custom Data Flow Component". Microsoft Developer Network. Microsoft. Retrieved 22 March 2013.
  12. "Developing a Custom Task". Microsoft Developer Network. Microsoft. Retrieved 22 March 2013.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.