@Craig
All the columns are concatenated using a single column (each delimited by a comma) and the output of the query is sent to a file. So instead of building separate ETLs for each output file, I can do this in a single ETL and also give the end users the flexibility to select as many number of columns as they want.
@Ray
I'm really sorry about that. Will make sure I don't repeat it.
Is it possible to pass a job parameter inside another?
Moderators: chulett, rschirm, roy
Resolution:
Instead of passing the entire query as a parameter I've passed only the necessary columns in one parameter and the filter conditions in another parameter. In the oracle stage i have something like
So instead of passing a parameter with another I used multiple parameters to achieve what i wanted.
Instead of passing the entire query as a parameter I've passed only the necessary columns in one parameter and the filter conditions in another parameter. In the oracle stage i have something like
Code: Select all
select #parcolumns# from #partablename# where #parconditions#