One way or another, you've got to create all of those files. Given that you need the destination to be dynamic, I can't think of a easy way to make...

Hmmm, wasn't clear to me! But now it is and my suggestion was not valid.

My first idea would be to use an Execute SQL task to populate an object variable...

I may be coming into this a bit late, but sorting can be done a bit more elegantly than that in .NET. Here's an example:

...

Pretty much what I meant.

Where are you getting the destinations from?

Strange requirement!

Can you do it just once and then do a file copy to the others - rather than running the data transfer over and over again?

I do not understand this question.

You seem keen on defending your solution to the death, when we have clearly pointed out...

No.

The requirement: ".. very next minute..."

Your solution misses that by up...

The File Watcher Task may be of interest.

Where is this 'equivalent table'?

It certainly looks like a data issue - are you sure that you have tested the package successfully in BIDS with the same data?

No doubt there is some underlying operation on the table which causes the condition to be true (insert, update etc). Have you thought about creating one or more triggers on...

Have a look in sysssispackages.

Add a Conditional Split after the MERGE JOIN to break your pipeline into two outputs: updates (Output1) and inserts (Output2).

Send Output1 to the OLEDB Command - as currently.

Output2 can map...

There's always a reason, though with that amount of information it's not easy to say more.

That sounds like a very slow way to insert records - can you describe the...

That's a good article, thanks! It's always good to have read about this stuff - one day, an ideal scenario will present itself and I'll be able to suggest a...