A great MSDN article about how you can squeeze the best performance out of your package dataflows.

Update: I just found some more performance tuning articles while doing some research on other SSIS related stuff.

Optimizing SSIS Package Performance Part 1 and Part 2 describe whats going on under the hood of the two main engines of SSIS: the runtime and the data-flow engine.

I just read an interesting article that helps me simplify my incremental load packages by using a checksum of the processed row to determine if the underlying data has changed. While scanning through the comments of the article, I realised that using the simple checksum component recommended in the article could eventually lead to missing a data change. Luckily there is a advanced hashing component available, supporting MD5 and SHA1 hashes.

I’m just trying to configure a custom logging mechanism for my SSIS packages and had some problems with the location and structure of the dbo.sysssislog table which is automagically created by the Integration Services (if you happen to use a integrated security database connection; else you need to grant CREATE rights to the corresponding database user). While googling I found some helpful tips by Joe The Business Intelligence Guy:

Read More