creating a file and then copying it: how to break the dependency between the 2 steps in SSIS
Oledb source editor pumps data into a flat file destination editor. after this data flow task, there is a file system task editor that copies this file into another OS drive location. This step is failing saying "The process cannot access the File ... because it is being used by another process."
how can we make sure that the first data task does not keep a hold on the file so that the next step does not fail? Is this plausible?
the idea i have mentioned above - do you anticipate this issue always? i did not seem to happen in SSIS 2005, but SSIS 2008 is perhaps more picky?