Download and Install

Download DTLoggedExec¶

DTLoggedExec can be downloaded from CodePlex, Microsoft's open source project hosting web site.

Download from CodePlex: http://www.codeplex.com/DTLoggedExec/Release/ProjectReleases.aspx

The code and the application are licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 2.5 Italy License: http://creativecommons.org/licenses/by-nc-nd/2.5/it/.

The "NoDerives" licensing limitation just means that if you want to contribute to the project you have to join codeplex and/or contact me so that I can add you to official authors list.

The "NonCommercial" licensing limitation just means that you cannot take the code and the executable and sell it. Of course, if you want to use it in your production enviroment, that's fine.

ZIP File Content¶

Within the zip archive you can download, you'll find, besides DTLoggedExec executable and source code, many other things that you may find of interest.

This is the content of the archive:

DTLoggedExec has been developed using Visual Studio (version 2008 actually), so you'll also find al the typical file for solutions, projects and so on.

DataFlowProfile¶

DataFlowProfile contains the files needed to import dataflow profiled data, as you can read here.

DTLoggedExec (all folders starting with)¶

These folders contains the source code of DTLoggedExec and its native Log Providers, along with executables.

DTLoggedExecDB ¶

This folder contains T-SQL script used to import Data Flow Profiles and CSV Logged data. Here you can also find the script used to create the DTLoggedExecDB to hold all imported data.

Log¶

Log folder contains the files needed to import data logged with the CSV Log Provider. You can read more here.

Samples¶

Guess? :) More information on all samples can be found in the Samples page.

Test Packages¶

Some test packages used by the above samples.

Install DTLoggedExec¶

DTLoggedExec is a 100% .NET application, and as such installation is as simple as a "copy file". Once you have downloaded the ZIP file, you can unpack it wherever you want. The package contains source code, samples, and of course the executables.

This is the folders tree for the executables:

DTLoggedExec
            \bin
                \Any
                    \Debug
                    \Release
                \x86
                    \Debug
                    \Release

The Any folder contains the executables compiled so that the .NET framework will automatically use 32bit or 64it code depending on the processor you're running on. If for compatibility reason with old drivers (i.e. Access Driver) you need to run always on 32bit mode, even on 64bit machines, the x86 version will help. Here the DTLoggedExec executable as been explicitly compiled to run always in 32bit mode, even on 64bit machines.

If you're intersted only in using DTLoggedExec to run your package you'll use the executables you can find in the Release subdirectory. The Debug subdirectory is used only by developers who needs to execute DTLoggedExec in debug mode.

Back in the root folder, the other directories contains samples, test packages, or source code. You'll find more information on these directories in the pages related to their subjects.

Best Practice Note¶

If you're interested only in using DTLoggedExec as tool for executing packages, and you're not interested in developing it, my suggestion is to create a C:\DTLoggedExec directory on your server, and here copy the Release subdirectory of both the Any and x86 folder. Copy also the directory needed to store DataFlowProfiling and CSV Logging. Although you can store these data wherever you want, if you keep the original folder structure you don't have to change anything to import data into the DTLoggedExecDB.

In such way you'll have a directory tree that will look like the following:

C:\
   DataFlowProfile
   DTLoggedExec
               \DTLoggedExec
                            \bin
                                \Any
                                \x86
   DTLoggedExecDB
   Log

If you're using DTLoggedExec on a clustered machine, instead of using C: drive use on of the shared drives.