When I use the OLB data source (SQL SERVER 2005), select * from tableA, thenuse several steps and then Union ALL and Fuzzy Match, the process worksfine. When I change the data source SQL to include two tables with a crossjoin, the new fields in Table B do not appear in the Union ALL or FuzzyMatch steps but do appear in all steps prior. The advanced editor refreshdoes not fix the problem. Deleting and recreating the Union ALL shows theTable A and Table B fields. Fuzzy Match is still incorrect. Deleting andrecreating Fuzzy Match fixes it.

This is because the UNION ALL component is an asynchronous component - all components prior to it must be synchronous because they are not exhibiting the same problems. Asynchronous components create a new buffer for their output which may or may not bear some resemblance to the input. It is actually possible to add the new output columns via the UNION ALL UI. Just don't expect them to be picked up automatically that's all. There is plenty of stuff about the web explaining more about synchronous and asynchronous components. -Jamie

Thanks for the help. I'll read in the Wrox book. There seem to be more issues with refresh not picking up the metadata or I'm using it wrong. When I create data viewers for steps in a data flow task and then deletethe steps, the data viewers still operate. I deleted allsteps in a task and the data viewers are still there. This is unexpected behavior. I suspose the correct sequence is to delete the data viewers first but I didn't. I would suggest that if the step has been deleted the associated data viewer should be deleted. Also I changed a SQL statement in the OLE DB source and created a bad column. This created a column previously not defined error. I fixed the sql and still got the error. One by one I deleted thesteps in the task in reverse order and still got the error. When I deleted the first step (OLE DB Source) I still got the error. Advanced editor refresh did not work. It seems like there should be a global refresh for a task that looks at the steps that are actually there.From reading some other entries, this problem may be a configuration file setting but I can't tell yet.

clecknerj wrote: Thanks for the help. I'll read in the Wrox book. There seem to be more issues with refresh not picking up the metadata or I'm using it wrong. When I create data viewers for steps in a data flow task and then deletethe steps, the data viewers still operate. I deleted allsteps in a task and the data viewers are still there. This is unexpected behavior. I suspose the correct sequence is to delete the data viewers first but I didn't. I would suggest that if the step has been deleted the associated data viewer should be deleted. That's very strange. Can you post a repro? -Jamie

I'll try but I only work on it during the weekends.

This is still a problem - or is next to impossible to find the config setting to force the refresh. I've increased a column size from 16 to 60 in SSMS, pulled up the SSIS package and, changed the column size on the source, refreshed the source and the target. When the package executed, it truncated at the old size limit (16), without the truncation warning message. I have refreshed, saved, logged out completely to no avail! I have disconnected the target connector (sql table), I have changed the source name which dropped the column definition, thinking if I re-enter the definition it would pick it up. Nothing! I've had issues with Refresh before, but it seemed if I saved, logged out and logged back in, it picked up the changes. Any feedback would be greatley appreciated. Thanks.