Make sure you specify that your Script Component is of type Transform when given the choice.

In the Input Columns tab, choose the email from your Flat File Source

In the Inputs...

Should be able to use the Execute SQL Task. Use SQLSourceType as Variable, and build a variable that appends the table name with TRUNCATE TABLE.

Hey there, saw you had sent me the email, dunno if that was before or after your last post. Do you still need any help?

Sure, send it to kramaswamy7@yahoo.com

BTW - you can't attach .dtsx files here, but you could zip them then attach the zip file.

The error is pretty self-explanatory. The table that you're trying to access doesn't exist.

If you attach your .dtsx file I can take a look and see if I can help...

Yeah t'was what I meant, my bad.

I wonder - if his data source isn't terribly large, might be easier to just use a FOREACH Loop, with the ADO collection, to...

You might be able to pull it off if you used a Script Task as your Data Source, fed the object variable into the Script Task, and then parsed it...

Something you might want to look into is SOUNDEX encoding.

Might be useful - try it out:

SELECT

SOUNDEX('John'),

SOUNDEX('Jon'),

SOUNDEX('Jonn'),

SOUNDEX('Jhon'),

SOUNDEX('Smith'),

SOUNDEX('Smth'),

SOUNDEX('Smithh'),

SOUNDEX('Smit')

All the firstnames and lastnames end up with the same SOUNDEX code. So you could...

You could use FORMATFILE for that. It allows you to specify the definition of the file you want to import. Should work for situations like that.

For 1), I've encountered similar problems when dealing with Excel files. Your best bet is to load the values into SSIS as DT_WSTR, give it a length of like, 12...

Alternatively, if you're sure there will only be two emails, you could always use the Script Component of the Data Flow Task. Have it be a Transform type Script Component,...

It should be like this:

File2 Source=>Lookup=>OLEDB Destination

Where the Lookup is going to query Table1, and retrieve the ID field as well as the field that File2 will match it on.

I assume you probably have new data inputted in one of your tables which is causing the rows you are returning to have some duplicates.

Try running the same query in...

Check your attachment, doesn't seem to have attached. I'll take a look at the package you posted and see if I can figure out why it's not working.

Okay, fair enough. Still doable with the same setup, but a bit more difficult.

Assuming the table definitions for all the tables are the same, just with different names, what you'll...