SQL Server Integration Services: Difference between revisions

Revision as of 17:50, 22 March 2013

Revision as of 17:56, 22 March 2013

Line 55:

DTUTIL 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 programmabilityprogramability==

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

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 62:

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_Server#SQL_Server_2005|2005]]/, [[Microsoft_SQL_Server#SQL_Server_2008|2008]]/, [[Microsoft_SQL_Server#SQL_Server_2008_R2|2008 R2]]/, and [[Microsoft_SQL_Server#SQL_Server_2012|2012]] editions except Express and Workgroup.

==See also==