You can use a RanK() or Row number() function in SQL to identify duplicate records and then use a Conditional Split and then Split the rows based on that...

P Jones (3/4/2010)

---

Yes you can - I spent ages with this problem in both 2000 dts and 2005 ssis.

In your Excel data source set the data access mode as SQL...

You seem to have the similar problem.... Check this post..you will find the explanation and answer

http://www.sqlservercentral.com/Forums/Topic876267-148-1.aspx#bm876827

sshah 25156 (3/3/2010)

---

Thank you divyanth.

For now quick fix changing a number field to text field in excel file worked but I need to have some permanent fix as user may...

Expressions are more friendly in SSIS and is always the best option..

You can achieve that by changing ecel properties Like IMEX =1 and also check HDR value. please check this article..it explains you clearly

http://www.sqlservercentral.com/articles/Integration+Services+%28SSIS%29/62697/

check this article

http://www.sqlservercentral.com/articles/Integration+Services+%28SSIS%29/62697/

you need to change the Excel properties

Rt clk on the Source/destination and choose advanced editor.. then in the columns check the properties of Input and output columns... That might help you resolve the error.. that msg...

Assuming that you have already changed the Folder share settings... what name did you give to your shared folder..

If you did not already change the Folder properties..do it by rt...

Did you try using Lookup component as i have suggested...

Do you see columns that you need in the Raw Source "Column" tab.. if yes then its a simple task

connect your raw source to OLE DB Command and then...

i suggest you use SQL statement instead to join the tables rather than using Merge join in SSIS... that will give you a better performance..

second option would be to...

The Path should always start with "/"

what is the destination path that you trying to send to.. may be we help you by correcting the path

you need to add "objvariable" as readonly and the other variable as writeonly and then use them in the script task... You can add them in the general tab of...

do you want to use the variable and pass it to the stored procedure on next execution???,.. i guess the only way would be store the value somewhere and then...