This is not really what you are looking for, but may help -- the book
"Oracle8 Design Tips" by Dave Ensor and Ian Stevenson had a good summary of
the usefulness of the Oracle8 features for designs. This is 8.0, though,
not 8.1.
HTH,
Diana
-----Original Message-----
Sent: Monday, March 05, 2001 7:41 PM
To: Multiple recipients of list ORACLE-L
Listers,
We will be upgrading from 7.3.4.3 to 8.1.7 (HP-UX 11.0 V2500). And this is a
bit of a broad question. Anyway, does anyone know of a paper, web site, etc
that goes through each of the features of 8.0 through 8.1.7 and provides
guidelines for estimating the potential performance return gained by
implementing each feature? I'm not asking for "just" a new feature list --
that is already known and readily available in the docs and various books.
Obviously, much of this is dependent upon the application and it's nature.
For example, using the cursor_sharing parameter. Might not be much help in
an app that utilizes binds exclusively, but, could be of benefit in an app
where there is great potential for SQL reuse (this app has a lot of "same"
SQL statements that differ only in the literal value specified). How might
one predict the impact of implementing cursor_sharing? Easy enough to look
at some things to gain a little insight, but, a little harder to gauge the
overall impact. Compressed indexes, partitioning, NOCOPY for PL/SQL package
parameter passing, temporary tables, bulk collect, bulk binds, native
dynamic SQL vs. DBMS_SQL, IOT's, LMT's, etc. The list is quite long. In many
cases, all that is provided in the documentation when discussing various
features is something like "the use of bulk binds can improve performance
considerably". Well, by how much? How to estimate? Enough so that we should
focus on bulk binds and/or bulk collects prior to looking at implementing
other features? I think you get the idea of the questions being asked.
It is easy enough to determine which concepts and features could be helpful
and can be applied. It is another matter determining which would provide the
most bang for the buck. The idea is to prioritize the features, focusing on
testing and implementing first those features that provide the biggest gain.
To do that, it would be helpful to have some type of reference that would
assist in predicting the improvements. Does such a document or reference
material exist? I know we can do this by benchmarking and comparing the
different options, and that may be the only route to go. Just hoping that we
could find a shortcut pointing us to the features to focus on first (based
on the characteristics of the app).
Sorry for such a broad (and long) question. But, if anyone has implemented
certain features where they saw a big performance gain, I would be
interested in hearing about them and the nature of the situation that
allowed for such gains to be made.
Regards,
Larry G. Elkins
[EMAIL PROTECTED]
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Diana Duncan
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
