When running SSIS components through SQL Server Agent jobs sometimes an error may appear and when viewing the job history you’ll see the helpful “To view the details for the execution, right-click on the Integration Services Catalog, and open the [All Executions] report”. If you attempt this you may get an “Out Of Memory” exception due to the sheer amount of logging your SSIS component is producing.
Connection string data should always be removed of obfuscated in source control. There are many approaches to accommodating this. Scott Hanselmann has a great post on this. Azure makes this even easier if you’re hosting a web app that’s referencing a database somewhere.
Hit an issue recently where a csv file was being transformed through an SSIS package but persisting to the database as zero value integers for all null value columns.