>An awesome product - I love it more every day.

Hi Kevin,
I had a few high level questions about SSIS that I hope somebody can give some insight on and maybe it will prompt some discussion.

First, how do you determine whether to use an SSIS package over a .NET console project hooked to your existing business logic?

Do your SSIS packages contain diverse functionality or just plain ETL? We load source flat files to our database, and we find that we have to check the source file to make sure it exists, to make sure it is not outdated (inspecting Last Modified Date on file), and whether it is empty or just header rows (inspecting the file size). We also archive files appending datetime stamps. We also have some conditional operations based on certain criteria (trigger files exist, day of week, etc.). We find that incorporating this functionality into an SSIS package can make it a little hard to manage and mantain. I admit that this difficulty might be related to our lack of experience with SSIS.

Why is it such a pain to work with an Excel file in SSIS? Crimany.

How do you store the source code for SSIS packages?

How do you use/manage config files?

TIA!