I no that there's a trick to "fool" SSIS using the
IF 1=2
Select
CAST(0 as int) as [Store No]
,CAST('' as varchar(10)) as MaxRptDate
,CAST('' as varchar(10)) as MinRptDate
,CAST('' as varchar(15)) as [UPC]
,CAST(0 as int) as [Quantity Sold]
,CAST('' as varchar(50))[Friendly Desc]
,CAST(0 as int) as [Vendor Item Number]
Well it's happened again where I have pointed the OLE DB to a stored procedure and someone changed the SP from table variables to temp tables and though the output columns are exactly alike - it broke the mappings and the SSIS package failed.
My questions:
1. Is there not a way to maually edit a settings file within the SSIS project to map the output to the flat file. The output from a temp table SP and the table variable SP is exactly the same so why can't we tell the SSIS this and it always works?
2. The whole idea of the stored procedure was the idea that it would be easier to modify without having to change the dtsx package. As long as the output columns were the same it should work but of course this isn't the case. Ideas? or is there just a rule of thumb that temp tables and SSIS are not compatible?