Comments on: SSIS Command Line Utilities part 1: dtutil

By: BI Monkey

BI Monkey — Wed, 02 Jun 2010 08:04:17 +0000

Dewi, that sounds pretty cool. I’ve been a bit more limited in terms of what we have used msbuild for – all i’ve used it for is just wrapping up packages into an installer. I probably wouldn’t make much sense of the code but it sounds like the sort of thing that would have a home on codeplex.

How would you use this in environments where TFS can’t talk to the target server? In one environment i’ve used it in, we have been constrained because our TFS box is in a separate domain to the test and prod boxes and there is no permitted path to communicate to those boxes. Hence using installers which are at least portable as files.

By: Dewi Felstead

Dewi Felstead — Wed, 02 Jun 2010 06:47:11 +0000

I too have found DTUtil useful for many of the same reasons listed here. One thing that I have been keen to do is integrate SSIS deployment tasks within an MSBuild script – this is obviously possible by calling the EXEC task from within a suitable target but is limited. The main reason for needing to do this is to automate the build and deployment of both our BI Databases and ETL packages.

I am in the process of creating a custom MSBuild ToolTask that wraps DTUtil functionality so it can be called from within an msbuild target – code can be made available if interested.

By: DimitryL

DimitryL — Sun, 16 May 2010 17:01:41 +0000

Great post! I find this particular article and the whole web site really useful and full of practical information. Currently, I am preparing for 70-448 exam; and I would like to thank author for such brilliant done work to create and constantly update the BI Monkey site.

By: dtexec - SQL Server Command Line Utility | BI Monkey

dtexec - SQL Server Command Line Utility | BI Monkey — Tue, 09 Mar 2010 09:57:12 +0000

[...] my previous post on dtutil, I looked at the command line utility to move and alter SSIS packages. In this post I will be [...]