-
how to tune this statement
Can any one guide to improve the performance of this statement
START WITH tree_parent = p_parent
CONNECT BY PRIOR tree_nodeid = tree_parent
Thanks in advance.
Last edited by vision; 08-25-2006 at 01:10 PM.
-
Based on this almost total lack of information? Not a chance.
-
 Originally Posted by slimdave
Based on this almost total lack of information? Not a chance.
Dave, are you new??
Of course this fine Gentleman can make that statement run faster. Everyone knows if you add the following to your init.ora all your statements will run faster.
There's also a hidden parameter that not a lot of people know about called
Code:
_auto_tune_all_sqlstatements=true
Oracle it's not just a database it's a lifestyle!
--------------
BTW....You need to get a girlfriend who's last name isn't .jpg
-
vision,
maybe you have to read those STICKY thread posted by marist and tarry first b4 anything else.
---------------
-
 Originally Posted by OracleDoc
Read long before of go_fast=3D true!
 Originally Posted by OracleDoc
There's also a hidden parameter that not a lot of people know about called
Code:
_auto_tune_all_sqlstatements=true
Are they version specific.
Can you brief more on these parameters?
"What is past is PROLOGUE"
-
 Originally Posted by OracleDoc
Dave, are you new??
Of course this fine Gentleman can make that statement run faster. Everyone knows if you add the following to your init.ora all your statements will run faster.
There's also a hidden parameter that not a lot of people know about called
Code:
_auto_tune_all_sqlstatements=true
Quiet, you fool! Are you mad, revealing these secrets?
-
Beware
Some where i read:
DO NOT use undocumented parameters that begin with underscores.
If you do, you may damage your database.
Many of these parameters cause side effects that if you are not aware of them, could seriously damage your database.
Until a parameter is documented, it is unsafe. Use at your own risk.
 Originally Posted by slimdave
Quiet, you fool! Are you mad, revealing these secrets?
Its no longer secret its been Googled.
anybody wanna use read the RED.
Know them, test them and then use at your own risk.
"What is past is PROLOGUE"
-
 Originally Posted by vision
Can any one guide to improve the performance of this statement
SELECT LEVEL AS tra_serial, tree_parent, tree_nodeid,
tree_id, tree_number, itm_crsref, itm_altdesc,
itm_lookupnum, itm_procat, itm_inact, itm_serial,
itm_type, itm_itemno, itm_traflg, itm_descrp, itm_id
FROM itmcat, sys_tree
WHERE itm_inact = 'A'
AND itm_id = tree_nodeid
AND tree_handle = 0
AND LEVEL < 6
START WITH tree_parent = p_parent
CONNECT BY PRIOR tree_nodeid = tree_parent
ORDER SIBLINGS BY tree_number
In general, to tune hierarchy query, an index on "CONNECT BY PRIOR" column is recommended, if the table is big.
Do you have an index on tree_nodeid column?
Can you post the execution plan?
Tamil
-
Tamil,
Does go_fast=true and _auto_tune_all_sqlstatements=true will work? and what are the side effects.
Undocumented parameters can be known only from you Guru's.
Enlighten the hungry souls...........Slimdave/Oradoc/and others
-
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|