Re: EXECUTE IMMEDIATE Question

It is very easy and very tempting to fall into the trap of building literal strings and then using execute immediate everywhere. This would probably result in an application that scaled very badly because of parsing costs and
library latch contention.

Try to restrict execute immediate to tasks which are inherently quite expensive (i.e. ones where the overhead is therefore
a very small percentage of the job), and where possible, make use of the USING
clause with bind variables to maximise
the reusability of the strings.

--
Jonathan Lewis

Host to The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Author of:
Practical Oracle 8i: Building Efficient Databases
See http://www.jlcomp.demon.co.uk/book_rev.html

Seminars on getting the best out of Oracle
See http://www.jlcomp.demon.co.uk/seminar.html

Screensaver or Lifesaver: http://www.ud.com
Use spare CPU to assist in cancer research.




Nadeem Kafi wrote in message ...


>Hi there,

>

>In my ongoing project, many of my procedures make heavy

>use of "Execute Immediate" PL/SQL command. Could somebody

>please comment on non-programming issues to consider

>when using this command? like performance e.g.

>

>TIA and Best Regards,

>Nadem Kafi.