Introduction

The logging information is very important and often underestimated. When everything works perfectly, nobody remembers that logging exists, but if it does not reverse, all eyes will be focused on logging to know what went wrong. In the production environment, the SQL Server Data Tools (SSDT) user interface, which provides useful information in real time about the rows passing through the Data Flow pipeline, will not be available. Packages are normally executed in batch mode at late night hours and if the logging saves just basic information, there will be less logging data to identify the cause of an unexpected error. In the previous versions, logging in SSIS was very basic and more detailed information required extra and duplicated work for developers, who spent too much time creating their own frameworks for SSIS logging. (Rest assured all those developers as your frameworks will still work on this version.) In SSIS 2012, two approaches for dealing with logging are possible...