This should help :

Have a derived col. Have three cols in there as (assume F1 is your excel col):

First_name

expression :SUBSTRING((REPLACE(F1,","," ")),1,FINDSTRING(F1," ",1))

Last_name

expression :

SUBSTRING(F1,FINDSTRING(F1," ",1) + 1,FINDSTRING(F1 + " ","...

Hope the variable @[user::connecitonstring] actually holds only the ServerName\Instance name and NOT the whole connection string.

(because the name sounds as if it holds the whole conn string). Please check.

(Well first....the company Konesans has something similar prebuilt in the form of a custom task. You might want to have a look at that)

Second....your most recent example is missing a...

Can be done in a variety of ways.....using the Message Queue like suggested by another member.

I would suggest something simpler....

1) Create a dtsx package(say checkFile.dtsx) having a simple script task...

You can assign the result set of your execute sql to a variable. Look under resultset in the ExecuteSQLTask. Map the resultset to a variable of Object type. Then in...

Lots of stuff out there to exactly do the thing you are rtying to achive. But in short :

...

By '30 different OLEDB Sources', i am assuming based on your question, you mean same server / same database but 30 different tables/views.

Yes, Script component could be...

The fifth node(Transaction List) does not just have a single node under it but multiple nodes. (In fact i would have thought that even with 'Balance' nodes, you would have...

Thats a very valid question......I assumed that the package will be running in an environment where these things are correctly set up meaning the package is selfaware(by way of variables...

Not sure what the problem is.....

I created an excel with different cells. Then merged the cells together. The excel gave a message back that the merged cells have different data...

there are basically two ways to do this :

1)

Change data access mode of the OLEDB Source to SQLCommand and write a query like :

select * from your_table where col1_value...

If you really want to directly check for a config file's availability, you can have a script task at the beginning of you package, which checks for the file (say...

The error message is quite clear.....please check the unique index constraint 'NK_QuotelAdditionalPlan' on your table. Basically some key value or values(if it happens to be a composite key) are coming...

I would create a sql agent job with first 3 steps as the run of your three SSIS packages(i think the sp is sp_start_job) and chain them such that next...

this should help......

If there are 10 different files each in different folder, I would suggest a script task with a C# script to delete a file and error out and...