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.
I was tasked with making changes to a fairly old SSIS component the other day which wouldn’t normally pose a problem but headaches and wasted time was heading my way.
Spent a few minutes trying to assign null to a derived variable as part of a script task transform. In my mind Row.CreatedDate = null would do it right?
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.