SQL Server Integration Services: Difference between revisions

Revision as of 00:08, 28 February 2013

Latest revision as of 00:11, 19 March 2025

(130 intermediate revisions by 70 users not shown)

Line 1:

{{short description|Database migration software}}

'''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.

{{Infobox software

| logo =

| screenshot =

| developer = [[Microsoft]]

| latest_release_version =

| latest_release_date =

| latest_preview_version =

| latest_preview_date =

| operating_system = [[Microsoft Windows]]

| genre = ETL Tools

| license = [[Proprietary software|Proprietary]] [[commercial software]]

| website = {{URL|https://technet.microsoft.com/en-us/library/ms141026.aspx}}

}}

'''Microsoft 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.

'''SSIS''' is a platform for [[data integration]] and [[workflow application]]s. It features a fast and flexible [[data warehouse|data warehousing]] tool used for data [[Extract, transform, load|extraction, transformation, and loading ([[Extract, transform, load|ETL)]]). The tool may also be used to automate maintenance of SQL Server databases and updates to multidimensional [[OLAP cube|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.<ref>{{cite web | title = Features Supported by the Editions of SQL Server 2014 | url = http://msdn.microsoft.com/en-gb/library/cc645993.aspx#SSIS|website=msdn.microsoft.com | publisher = Microsoft Developer Network | access-date = 20 August 2014}}</ref> 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 (software)|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 in which tofor writewriting 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).<ref>{{Cite web|url=http://sqlmag.com/sql-server-2014/q-where-business-intelligence-development-studio-bids-sql-server-2014|title = IT Pro}}</ref><ref>{{Cite web|url=http://blogs.msdn.com/b/analysisservices/archive/2013/03/06/sql-server-data-tools-business-intelligence-for-visual-studio-2012-released-online.aspx|title=DevBlogs}}</ref>)

; 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 &mdash; 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 (whichthat can copy or move files) to the data transformation task. The data transformation task actually copies data; it implements the [[Extract, transform, load|ETL]] features of the product

; Variables : Tasks may reference variables to store results, make decisions, or affect their configuration.

; Streamlined Data Integration: SSIS offers a visual interface and pre-built components to simplify the process of extracting data from various sources, transforming it, and loading it into target destinations. This reduces development time and effort compared to writing custom code. <ref>{{cite web | url = https://techunwrapped.com/ssis-816-definition/ | title = SSIS-816: Definition, History, and ETL Capabilities |work=Techunwrapped | date = 6 September 2024 | publisher = Techunwrapped.com}}</ref>

; 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.

; 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 (which 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

; 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.

; 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 &mdash;such as cleaning up after errors.

; Variables : Tasks may reference variables to store results, make decisions, or affect their configuration.

; Parameters (SQL Server 2012 Integration Services) : Parameters allow you to assign values to properties within packages at the time of package execution. You can 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.

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

Line 22 ⟶ 38:

===Features of the data flow task===

[[File:SSIS workflow.png|thumb|An example of a SQL Server Integration Services (SSIS) workflow, by visually programming the steps needed to transform data from source to destination.|alt=Diagram with seven nodes. 1: OLE DB Source (Source Table), flows to 3: Sort Source Table, flows to 5: Merge Join. Another flow goes from 2: OLE DB Source (Dest Table), flows to 4: Sort Dest Table, flows to 5: Merge Join. From 5: Merge Join, the flow goes to 6: Conditional Split, flows to 7: OLE DB Destination.]]

SSIS provides the following built-in transformations:

SSIS provides the following built-in transformations:<ref>{{cite web | title = Integration Services Transformations | url = http://msdn.microsoft.com/en-us/library/ms141713.aspx|work=Microsoft Developer Network | publisher = Microsoft | access-date = 22 March 2013}}</ref>

{{Div col|colwidth=18em}}

* Conditional Split

* Multicast

* Union-All, Merge, and [[Sort-merge join|Merge Join]]

* Sort

* Fuzzy Grouping

* Lookup and [[Fuzzy logic|Fuzzy]] Lookup

* Percentage Sampling<ref>[http://msdn.microsoft.com/en-us/library/ms139864.aspx creates a sample data set by selecting a percentage of the transformation input]</ref> and Row Sampling Transformation.

* Copy/Map, Data Conversion, and Derived Column

* Aggregation

* Data Mining Model Training, Data Mining Query, Partition Processing, and Dimension Processing

* [[Pivot]] and Unpivot

* [[Slowly Changing Dimension]]

* Script Component

* Audit

* Cache Transformtransform<ref>[{{cite web | url = http://msdn.microsoft.com/en-us/library/bb895264 writes| datatitle from= aCache connectedTransform|work=Microsoft dataDeveloper sourceNetwork in the| datapublisher flow= toMicrosoft a Cache| access-date = 22 connectionMarch manager]2013}}</ref>

* Copy/Map

* Export and Import Column

* Data conversion

* OLE DB Command

* Data mining model training

* Row Count

* Data mining query

* [[term extraction|Term Extraction]]

* Dimension processing

* [[Derived column]]

* Export and Importimport Columncolumn

* For loop container

* Foreach loop container

* ([[Fuzzy_logic|Fuzzy]]) lookup

* [[Fuzzy_logic|Fuzzy]] grouping

* OLE DB Commandcommand

* Partition processing

* Percentage sampling<ref>{{cite web | url = http://msdn.microsoft.com/en-us/library/ms139864.aspx | title = Percentage Sampling Transformation|work=Microsoft Developer Network | publisher = Microsoft | access-date = 22 March 2013}}</ref>

* [[Pivot table|Pivot]]

* [[Pivot table|Unpivot]]

* Row Countcount

* Row Samplingsampling

* Row sampling transformation

* Script Componentcomponent

* [[Slowly Changingchanging Dimensiondimension]]

* [[termTerm extraction|Term Extraction]]

* Term Lookup

{{div col end}}

* Row Sampling

The Conditionalconditional Splitsplit transformation is used to speedconditionally uproute therows queryto onother the sourcetransformation tableobjects based on a particular condition. It is similar to the "<code>[[conditional (programming)|if.. … else]]</code>" construct in the C language.

<!--this is not good for etl------>

=={{Anchor|A-tools}}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.<ref>{{cite web | url = http://msdn.microsoft.com/en-us/library/ms162810%28v=sql.105%29.aspx | title = dtexec Utility (SSIS Tool) | access-date = 2013-03-24 | publisher = Microsoft|work=Microsoft Developer Network}}</ref><ref>{{cite web | url = http://www.databasejournal.com/features/mssql/article.php/3897236/Executing-SSIS-Packages-Using-DTExec.htm | title = Executing SSIS Packages Using DTExec | access-date = 2013-03-24|date=2010-08-09 | publisher = Database Journal|author=Marcin Policht}}</ref> 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, again from the [[Windows command prompt|command prompt]].<ref>{{cite web | url = http://msdn.microsoft.com/en-us/library/ms162820%28v=sql.105%29.aspx | title = dtutil Utility (SSIS Tool) | access-date = 2013-03-24 | publisher = Microsoft|work=Microsoft Developer Network}}</ref><ref>{{cite web | url = http://www.databasejournal.com/features/mssql/article.php/3734096/Using-dtutil-to-copy-SSIS-packages-stored-in-SQL-Server.htm | title = Using dtutil to copy SSIS packages stored in SQL Server | access-date = 2013-03-24|date=2008-03-20 | publisher = Database Journal|author=Yan Pan}}</ref> 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.

The Bulk Copy Program (BCP), is a [[Console application|command-line tool]] used to import or export data against a [[Microsoft SQL Server]],<ref name="FIPADA">{{cite book|last1=Rankins|first1=Ray|last2=Bertucci|first2=Paul|last3=Jennsen|first3=Paul|date=December 2002|title=Microsoft SQL Server 2000 Unleashed|edition=2|publisher=Sams|___location=Indiana|isbn=9780672324673|oclc=474621100|pages=86–87}}</ref> or [[Sybase database]].<ref>{{cite book|url=http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc30191.1550/html/utility/X14951.htm|work=[[Sybase]]|accessdate=14 May 2021|title=Adaptive Server Enterprise 15.5|chapter=Chapter 7: Utility Commands Reference}}</ref>{{better source needed|date=May 2021}}

==Extensibility and programmability==

Users may write code to define their own connection objects, log providers, transforms, and tasks.<ref>{{cite web | title = Developing a Custom Data Flow Component | url = http://msdn.microsoft.com/en-us/library/ms136078.aspx|work=Microsoft Developer Network | publisher = Microsoft | access-date = 22 March 2013}}</ref><ref>{{cite web | title = Developing a Custom Task | url = http://msdn.microsoft.com/en-us/library/ms135965.aspx|work=Microsoft Developer Network | publisher = Microsoft | access-date = 22 March 2013}}</ref>

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

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.

Line 63 ⟶ 88:

Within limits, SSIS packages can load and call [[Assembly (CLI)|CLI assembly]] [[Dynamic-link library|DLL]]s, providing access to virtually any kind of operation permissible by the .NET [[Common Language Runtime|CLR]].

SSIS can be used on all SQL Server [[Microsoft_SQL_ServerMicrosoft SQL Server#SQL_Server_2005SQL Server 2005|2005]]/, [[Microsoft_SQL_ServerMicrosoft SQL Server#SQL_Server_2008SQL Server 2008|2008]]/, [[Microsoft_SQL_ServerMicrosoft SQL Server#SQL_Server_2008_R2SQL Server 2008 R2|2008 R2]]/, [[Microsoft_SQL_ServerMicrosoft SQL Server#SQL_Server_2012SQL Server 2012|2012]], [[Microsoft SQL Server#SQL Server 2014|2014]] and [[Microsoft SQL Server#SQL Server 2016|2016]] editions except Express and Workgroup.

==See also==

* [[Data Transformation Services]]

==References==

{{reflistReflist|2}}

==External links==

* [http://www.microsoft.com/sqlserver/2008/en/us/integration.aspx SQL Server Integration Services official site]

* [http://msdn.microsoft.com/en-us/sqlserver/cc511477.aspx SQL Server Integration Services (SSIS) Resources]

* [http://social.technet.microsoft.com/Forums/en/sqlintegrationservices/threads SQL Server Integration Services Discussion Forum]

* [http://www.sqlis.com/ SQLIS.com]

* [http://www.bi-dw.info/microsoft-ssis.htm SSIS resources]

* [http://www.microsoft.com/Sqlserver/2005/en/us/compare-features.aspx SQL Server 2005 version comparison]

* [http://ssisctc.codeplex.com/ SSIS Community Tasks and Components]

* [http://sqlblog.com/blogs/andy_leonard/ SSIS 2005/2008 Design Patterns, Tips, and Tricks]

* [http://www.cozyroc.com/search-scripts/ SSIS Scripts]

[[Category:ETLExtract, transform, load tools]]

{{data warehouse}}

[[Category:Microsoft database software]]

[[Category:ETL tools]]

[[Category:Microsoft server technology]]

[[Category:Microsoft database2005 software]]