The problem you are having is that the table needs to exist before you can create the required mapping meta data.

But there is a way round this:

Allow the build task...

OK, now we're really getting somewhere 🙂

I will tell you what I would do - others would certainly have their own ideas.

1) Build the destination table now, including all of...

You have not answered all of my questions, so it's difficult for me to answer.

Does your destination table already exist? If so, what's the problem? Just go ahead and import....

Yeah, the meta data issue is going to make this a tough job for you, because you need a dynamic data flow and SSIS isn't good at that.

Cozyroc has an...

This is an unusual requirement - let's make sure I understand.

Say your input file has 10 columns and, out of those, 8 columns contain only nulls.

You want to load...

ar-727381 (9/23/2009)

---

i cannot untick them because there are around 40 columns with 100's of rows in the csv file. so checking if a column is null or not is not...

I am interested to hear what the business need is behind this requirement - can you provide an overview? There may be other ways of addressing it.

After reading this thread, I suspect his head will be quite big enough!

Here is an example, in pseudo-code.

1) Traditional Loop/Cursor

Foreach Executive in Person

Set Salary = Salary * 1.1

Next...

Elliott W (9/22/2009)

---

Phil Parkin (9/22/2009)

---

An example of your input data would paint the picture much more completely than just words, no matter how detailed your verbal explanation ... So far...

Elliott W (9/22/2009)

---

Phil Parkin (9/22/2009)

---

Or possibly (thinking a level up) a parent package that concurrently runs multiple occurrences of the same child package, with appropriate parameters.

I haven't tried that -...

Sounds like you got it working well - good stuff:cool:

An example of your input data would paint the picture much more completely than just words, no matter how detailed your verbal explanation ... So far I have a picture...

Use an Execute SQL task (select count(*) from ...) to assign the count to a package variable (which you will have to create) at control flow level and then use...

Or possibly (thinking a level up) a parent package that concurrently runs multiple occurrences of the same child package, with appropriate parameters.

I haven't tried that - and it doesn't sound...

Or put some other unused character there...