This fourth and final installment looks at making the database run faster and the DBA-developer relationship. This manuscript is Chapter 1 'Developing Successful Oracle Applications' from the Wrox Press book Expert One on One: Oracle.
Tutorial Details:
Database Oracle Expert One-on-One: Oracle: Part 4 Tutorial
How Do I Make it Run Faster?
The question in the heading is one I get asked all the time. Everyone is looking for the fast = true switch, assuming 'database tuning' means that you tune the database. In fact, it is my experience that more than 80 percent (frequently much more, 100 percent) of all performance gains are to be realized at the application level ? not the database level. You cannot tune a database until you have tuned the applications that run on the data.
As time goes on there are some switches we can 'throw' at the database level to help lessen the impact of egregious programming blunders. For example, Oracle 8.1.6 adds a new parameter, CURSOR_SHARING=FORCE. This feature implements an 'auto binder' if you will. It will silently take a query written as SELECT * FROM EMP WHERE EMPNO = 1234 and rewrite it for us as SELECT * FROM EMP WHERE EMPNO = :x. This can dramatically decrease the number of hard parses, and decrease the library latch waits we discussed in the Architecture sections ? but (there is always a but) it can have some side effects.
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: Database Oracle Expert One-on-One: Oracle: Part 4 Tutorial
View Tutorial: Database Oracle Expert One-on-One: Oracle: Part 4 Tutorial
Related
Tutorials:
|
Displaying 1 - 0 of about 0 Related Tutorials.
|
|
|
|
