Hi,
i'd like to use an oraoci8 plug_in with the option "User Defined SQL Query File" because i have a very complicated query.
i set the options... but:
where can i specify the name and the directory of file with the query?
tanks in advance
Mario Loreti
"User Defined SQL Query File" in a ORAOCI8 Plug_In
Moderators: chulett, rschirm, roy
Re: "User Defined SQL Query File" in a ORAOCI8 Plu
:D, No such thing. You enter the query in the stage itself.eoyylo wrote:Hi,
i'd like to use an oraoci8 plug_in with the option "User Defined SQL Query File" because i have a very complicated query.
i set the options... but:
where can i specify the name and the directory of file with the query?
tanks in advance
Mario Loreti
Ogmios
Sure there is! And yes, when you specify SQL Query File in the stage what you input is the full path to the file - in the same place that you would put any Custom SQL. You can also right-click on the stage and specify 'Grid Style', then where you put it is a little more obvious.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
I've seen it used, it's handy if you want a DBA team to be responsible for your complex SQL queries. They own and maintain and optimise the SQL scripts and save them to a directory on the DataStage server, they don't need to do anything with with DataStage, they just have to make sure the column select list doesn't change. They can fix up statements without requiring a recompile of the DataStage job.
For simple queries I would avoid them, why have code sitting outside of DataStage? Just another thing to get lost or forgotten during delivery.
For simple queries I would avoid them, why have code sitting outside of DataStage? Just another thing to get lost or forgotten during delivery.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
I wholeheartedly agree! I've used it (once!) in the past for dynamically generated SQL - one job generates the SQL statement and writes it to a file and the next runs using that SQL File. Not something to be doing on a regular basis unless you've got no other way to manage it. IMHO, of course.vmcburney wrote:For simple queries I would avoid them, why have code sitting outside of DataStage? Just another thing to get lost or forgotten during delivery.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers