Re: Wrapping all tables with packages and scalability

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Sun, 2 May 2004 17:02:10 +0100
Message-ID: <005201c4305e$d3526cf0$7102a8c0@Primary>

If you use the mechanism

open ref cursor for SQL statement

this requires an explicit parse call -
which can still introduce undesirable
contention in a high-activity even if
the parse call is only a 'soft' parse.

Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

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

June 2004 UK - Optimising Oracle Seminar July 2004 USA West Coast, Optimising Oracle Seminar August 2004 Charlotte NC, Optimising Oracle Seminar September 2004 USA East Coast, Optimising Oracle Seminar September2004 UK - Optimising Oracle Seminar

Original Message ----- From: "Ryan" <ryan.gaffuri_at_cox.net> To: <oracle-l_at_freelists.org> Sent: Sunday, May 02, 2004 4:32 PM Subject: Wrapping all tables with packages and scalability

I met a guy about 2 months ago who used this design concept. Its basically object oriented abstraction in the database. Each table has a package. Each package has all the methods that operate on the table(all the SQL). SQL is returned with REF Cursors. I know Steve Fuerstein advocates this. He was stating that in a high transaction system with a max of about 700 transactions/second, he was unable to get his parse/execute ratio above 75%. He noticed that Oracle did not always use bind variables on the dictionary cache elements used by these packages.

Anyone else notice this? I have not tested it.

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.
--

Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html

Received on Sun May 02 2004 - 10:59:03 CDT