I am wondering whether the fact that you used file-level copy with the packages has confused SSIS because of the duplicate IDs all over the place.

You may like to try...

Sorg should be joined to source_id, not destination_id.

The rest should be ok ... as long as you do not need sorg later on in the dataflow.

Build a mapping table (OldID, NewID) and then use a Lookup transformation to lookup the new ID based on the old ID ... much easier than building a mega-complicated nested...

How did you make the copies?

This also sounds like a maintenance nightmare for the future. Is there any reason why you don't do all the processing in the same package?

Puzzling.

OK, please try opening the advanced editor for your data source.

Have a look at Input and Output properties. Check External and Output columns for SectionTitle - should be TextStream (at...

murugappan.kathiresan (4/12/2010)

---

Phil,

This is my scenario...

I've one excel file, in that file i've one column called Allowance which has only numeric values if it is 0 then the user will enter...

Try putting a data conversion task after your source component. Convert the text field to string(4000) and map the converted field to your destination.

Are you saying that the data type of Allowance is numeric?

That would suggest that "-" is a valid numeric entry - as far as I know, it is not.

So ... the data type of your derived column must also be float?

But you are setting the value of this column to Allowance, which is a string ...

What's the datatype/length of 'LongDescription'?

What is the data type of Allowance?

Correct!

No. You use SQL Server Business Intelligence Development Studio (BIDS) to edit packages.

Jason Coleman (4/9/2010)

---

Yep...thats finally what I have had to do.

Seems strange though that the final task seems to transform the data on its own. even if u tell it...

Once you have a string field which contains, for example .75

you can add a derived column that prepends a 0

the string is then 0.75 and that is what will go...