Script Task Exception Handling in SSIS

When working with Script Task of SQL Server 2008 Integration Services, it is important to ensure that your custom code complies with the most elementary programming practices. Learn how to handle unexpected errors that interfere with the successful execution of your code.

Implementing Execution Log Reports on 32-bit SQL Server 2008 R2

This article covers how to implement the SQL Server 2008 Execution Log DB and package on SQL Server 2008 R2

Running a SSIS Package from SQL Server Agent Using a Proxy Account

Recently when I created a SQL Server Agent job to execute a SSIS package, it failed with the message "Non-SysAdmins have been denied permission to run DTS Execution job steps without a proxy account.". What is this exception about? What causes it and how do I resolve it?

SSIS Execute Package Task

Querying Active Directory using SSIS Script Task

One of the most distinguishing characteristics of Control Flow Script Task available in SQL Server 2008 Integration Services is its flexibility. This article demonstrates some of these capabilities by describing an approach that employs the Script Task to query data residing in an Active Directory domain database.

Capturing and Logging Data Load Errors for an SSIS Package

In an ETL solution, error logging is a fundamental requirement for various aspects of the application and is very useful at various stages of the ETL execution life-cycle. Let's consider a scenario where our requirement is to insert records into a SQL Server table. The package should attempt loading all the records and whichever records fail, error details reported by the database engine should be reported. We will look at how to implement this in a SSIS package.

Creating Dynamic Outputs in SSIS to an SQL Database

This article shows how you can dynamically split data based on transaction type to its own destination table using Integration Services.

Intelligent Conditional Split in an SSIS Package

Conditional Split is one of the most commonly used transforms in any SSIS Package development routine. The limitation with conditional split is that any record that satisfies the first condition from the conditions list is routed to its corresponding path exclusively. In a logical sense, a record might satisfy more than one condition and one might want the record to be routed to all paths for processing, but with the Conditional Split transform this is not possible. We need a more intelligent conditional split where we can selectively route the records to more than one output path. In this tip we will look at how to facilitate this intelligent conditional split.

Using SSIS Logging to Resolve Runtime Errors and Performance Issues

Runtime errors and performance issues can be difficult to identify and resolve. One of the primary methods that assist with their resolution involves generating logs, which contain records of events taking place during code execution. This article provides a comprehensive overview of logging options available in SQL Server 2008 R2 Integration Services.

Protect the Excel files generated by SSIS package-Part I

It is not only the data within the database that requires protection but any report generated using SQL Server needs to be protected before being mailed