That is indeed very odd. Maybe even SSIS can have the Monday blues?

If you use trim functions in the lookup component, don't forget to provide aliases for the columns!

(sorry, I forgot to mention that sooner :))

If you don't do that, every column...

Nice question, thanks. A good follow up of the previous rounding questions.

And a great explanation.

Also, trim the columns in your lookup component, you never know. I believe you can only use LTRIM and RTRIM there.

SanjayAttray (8/16/2010)

---

Since, it doesn't make much sense, if you want to put duplicate value in identity column then why add identity option to column int. Just leave it as...

How is the OLE DB Destination component configured? Did you use the fast load option and if yes, how did you configure the options?

Also check if there is some case sensivity.

It is a good practice to put everything in either lowercase or in uppercase, so that there can be no issues regarding the...

In the beginning of the article, it is explained how you can add a variable to the variable mappings of the for each loop container. This variable will contain the...

You can use the dtutil utility in the command line to achieve this:

http://msdn.microsoft.com/en-us/library/ms162820.aspx

You need a seperate data flow for each type of source. Even if you have 2 excel files but with different structure, you need 2 different dataflows. Then choose conditionally...

Nice question. Usually an Identity column is used as a primary key (and thus having a unique clustered index), which will prevent the insertion of duplicate values.

The connection string is used to connect to a database using OLE DB, right?

My connection strings look the same, but I don't have the Application Name part.

ktlady (8/12/2010)

---

1) I am looping through the excel files and then sheets to get data. And I have two variables: FileName and SheetName.

In the ADO Net Source specification, i was...

It seems that you are trying to insert a string into a variable of datatype binary, which is causing the error.

You said that your package variables are of the string...

You have several options:

- split out the code in multiple expressions. (not good for maintenance)

- create a stored procedure at the beginning of your package. This sp contains your code...