SQL Server Integration Services: Difference between revisions

Revision as of 15:23, 21 July 2014

Revision as of 21:31, 22 July 2014

Line 51:

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)|accessdate=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|accessdate=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 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)|accessdate=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|accessdate=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.

==Extensibility and programmability==