Friends,
SSIS include many default providers to log the information of SSIS package. Let’s see about each one in this post. We have the following types of LOG providers in SSIS.
- SSIS Log Provider for Text Files
- SSIS Log Provider for SQL Profiler
- SSIS Log Provider for SQL Server
- SSIS Log Provider for Windows Event Log
- SSIS Log Provider for XML Files
You can see all there under SSIS Menu–> Logging wizard as shown below.
PFB the details of each Provider.
- SSIS Log Provider for Text Files: This provider is used to store log information to a CSV file on the file system. This provider requires you to configure a File Connection object that defines the location of the file. Storing log information in a text file is the easiest way to persist a package’s execution. Text files are portable, and the CSV format is a simple-to-use industry-wide standard.
- SSIS Log Provider for SQL Profiler: This provider produces a SQL Profiler trace file. The file must be specified with a trc file extension so that you can open it using the SQL Profiler diagnostic tool. Using SQL profiler trace files is an easy way for DBAs to view log information. Using Profiler, you could view the execution of the package step-by-step, even replaying the steps in a test environment.
- SSIS Log Provider for SQL Server: This provider sends package log events to a table in the specified SQL Server database. The database is defined using an OLE DB Connection. The first time this package is executed, a table called sysdtslog100 will be created automatically. Storing log information in a SQL Server database inherits the benefits of persisting information in a relational database system. You could easily retrieve log information for analysis across multiple package executions.
- SSIS Log Provider for Windows Event Log: This provider sends log information to the Application event store. The entries created will be under the Source name SQLISPackage. No additional configuration is required for this provider. Logging package execution to the Windows Event Log is possibly the easiest way to store log events. The Windows Event Log is easy to view and can be viewed remotely if required.
- SSIS Log Provider for XML Files: This provider stores log information in a specified XML file on the file system. The file is specified through a File Connection object. Make sure you save the file with an xml file extension. Logging events to XML inherits the advantages of the XML specification. XML files are very portable across systems and can be validated against a Schema definition.
You can choose the provider of your wish. You can also choose more than one. It all depends on the requirements by the clients.
Regards,
Roopesh Babu V
