October 10, 2016 at 8:21 am
I have a quick question, Instead of hardcoding or pasting a query in Execute sql task (SSIS package) Is there a way not to hardcode it?
I mean source is anywhere and it does the SSIS package and loads into destination.
Note : Different connections source is and the destination is..
Any Ideas Plz..
October 10, 2016 at 8:37 am
mcfarlandparkway (10/10/2016)
I have a quick question, Instead of hardcoding or pasting a query in Execute sql task (SSIS package) Is there a way not to hardcode it?I mean source is anywhere and it does the SSIS package and loads into destination.
Note : Different connections source is and the destination is..
Any Ideas Plz..
An ExecuteSQL task can take a variable as its source. The variable can be a parameter, which is passed to the package at run time. Is that what you are looking for?
When you talk of source and destination, that sounds more like a data flow than an ExecuteSQL task, so I'm not sure exactly what you are looking for here.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 11, 2016 at 2:56 pm
You can write stored procedure and execute it in executesql task and pass value to result set (variables).
or In dataflow task , " query from variable" can be used.
October 13, 2016 at 7:30 am
The query which I am using in the package is just select query -- it is not using any variables.
it is coming from different database we are using it as a source int he package as of now I am just hardcoded in execute sql task...
instead of hardcoding is there any option?
can u tell me the process.any link is there to get me some idea.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply