I think your best option is to use a script task.

This script task will open a file, read a line and split that line into multiple strings (according to the...

Well, for the first 19 you can use a for each loop.

But you can't use a flat file source/destination if your columns change each time, so you're stuck with scripting.

One...

It depends I guess 🙂

It depends on what you're trying to do in your package. If you write/delete twice to the same table, then maybe yes, there will be some...

It seems that the caps-lock on your keyboard is broken...

Where did you try to login to SSAS? BIDS or SSMS?

To answer your question which components you need:

1. Execute SQL Task in the Control Flow

1.a Add a data flow task after the previous task with a precedence constraint (green arrow)

2....

I have also encountered this issue many many times.

Sometimes the task aren't visible, or only partially visible.

Or, the arrows don't run in a straight line, so I re-draw them. However,...

According to MSDN, you should be able to install it on Vista:

http://msdn.microsoft.com/en-us/library/ms143506.aspx#DEx64

I don't know how you call the SSIS job exactly, but you can pass parameters with the SET command.

You can find more information at the following URL:

http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/d1d4df24-c511-4747-b395-040524d4f8a9

You could add a Data Conversion component that converts all the columns to the length of the OLE DB Destination columns. That should get rid of all the warnings.

That's because it...

In SSIS 2005, the Flat File source is quite static with delimeters, meaning the numbers of columns are fixed. (otherwise SSIS can't map the metadata to corresponding columns in the...

I believe that in the Execute SQL Task, the ? are mapped to the variables regarding their ordinal position. Since SSIS can't know if you are using two distinct variables...

You could place different data flows in one single sequence container. Each dataflow reads a file and processes it.

fm447k (3/17/2010)

---

I'm able to import an Excel file on my local machine without any problems. However some of the columns are null when I run the code on the production...

Just to make sure, put another (correct) filepath in your variable (pointing to another file).

Then run your package so you can be sure that SSIS takes the correct file at...