Besides the obvious, Execute SQL Task being used in Control Flow, andOLE DB Command being used in Data Flow what is the difference between the two? Is one supposed to useExecute SQL Task to produce a result set that then gets handed over toData Flow and OLE DB Command ? Everything that I have seen onOLE DB Command is pretty much execution of a Stored Procedure with ? parameters. It seems as though I got to a point where I had to perform my data edits pretty much entirely in a Stored Procedure executed byOLE DB Command rather than trying to use the SSIS GUI for everything. I didn't really see in any of my Google searches out there that simply usedOLE DB Command as a straight parameterized SQL against tables for editing and cleansing purposes and handling returns back from SQL Server for COUNT(*), etc..
I know I have posted multiple forums out there regarding this issue but I cannot seem to get a straight answer and some solid direction. So for now, myExecute SQL Task gives me my editable result set and then control is handed off toData Flow and ultimately to my Stored Procedure executed by an OLE DB Command which pretty much does the chunking for me and performs my data edits and handles my record anomalies through SQL Server Table data stores accordingly or sets flags accordingly if the data passes.
I welcome your thoughts and Thanks for your review and Thanks in advance for any replies and direction that anyone might provide.