Logging Package Execution
Microsoft SQL Server Integration Services includes logging features that expose run-time events for logging, support a diverse set of logging providers, and provide commonly requested information for logging. Information can be logged to text files, SQL Server Profiler, the sysssislog table in a SQL Server database, the Windows Event Log, and XML files. For more information, see Integration Services Log Providers.
Packages can be configured to use logging by using SSIS Designer, the graphical tool for creating packages that Integration Services provides, or programmatically. For more information about how to enable a package and its containers and tasks for logging, see Implementing Logging in Packages.
You can also include logging when you run a package using the dtexec command prompt utility. For more information about the command prompt arguments that support logging, see dtexec Utility (SSIS Tool).
After a package finishes running, you can view the run-time information in the package logs.
The following table describes the location of the logs to which Integration Services log providers write.
The File connection manager that the log provider uses specifies the path of the text file.
SQL Server Profiler
The File connection manager that the log provider uses specifies the path of the file used by SQL Server Profiler.
Windows Event Log
The Application log in Windows Event Viewer contains the Integration Services log information.
The OLE DB connection manager that the log provider uses specifies the SQL Server database that contains the sysssislog table with the log entries.
The File connection manager that the log provider uses specifies the path of the XML file.
Blog entry, Configuring SQL Agent Jobs to Write to Windows Event Log, on mssqltips.com.
Tool, SSIS Log Analyzer. on CodePlex.com.
Tool, DTLoggedExec, on CodePlex.com.
Video, SSIS Log Analyzer (SQL Server video), on technet.com.