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

SSIS Events and Handlers

Explore how SQL Server 2008 Integration Services' events are triggered during package execution and the ability to react to their outcome through event handlers.

SSIS Package Execution

SSIS Control Flow

Top 10 SQL Server Integration Services Best Practices

Learn the top 10 best practices for large scale SSIS packages from a real world DBA.

SSIS Scripting

Automatic Restart of SSIS packages after Failover or Failure

SSIS makes it possible to minimize work lost by starting after the last successfully executed control flow task upon restarting a failed package. From there, one challenge many seek to overcome is automatically restarting that package at that point without any manual intervention. This would make it possible for your SSIS packages to be running, your cluster to failover, and your SSIS packages to restart and complete without you having to respond to the failover and restart them.

Parsing an ADO result set into a comma separated string in SSIS

This article describes a way to parse a result set in SSIS using For each loop container, variables and SQL task.

Integration Services Sources

A deadlock was detected while trying to lock variables in SSIS

Error: 0xC001405C at SQL Log Status: A deadlock was detected while trying to lock variables "User::RowCount" for read/write access. A lock cannot be acquired after 16 attempts. The locks timed out. Have you ever considered variable locking when building your SSIS packages? I expect many people haven’t just because most of the time you never see an error like the one above. I’ll try and explain a few key concepts about variable locking and hopefully you never will see that error