Knowing SQL tuning can be a complicated process. Essentially, Oracle performance tuning is conducted through an SQL statement. This is set up in order to express precisely what you need, nonetheless it won't tell the server how to accomplish it. By way of example, you may ask your server to search for all customers within a particular geographical region. The server then parses this statement and in case there are no syntax errors, it will be able to carry on. The server then determines the very best way to come up with the results. By way of example, it may read the entire client table or possibly it might use the index. The actual server merely measures up the cost when it comes to the time of all probable approaches. This is called a query plan or an execution plan.
In a query plan, there are several quite primitive functions. Anybody who is actually involved in performance tuning in Oracle needs to be mindful of this. Most of these operations consist of just how to use an index, tips on how to read a full table, just how to execute a hash join as well as how to perform a nested loop for instance. Just about all of these procedures will have an output, which is their own result set. The actual inputs, however, can be either single or multiple. Inputs are attached to the output, and that's why a query plan might be graphically symbolized as a tree, which is amongst the Oracle 11g new features. This shows exactly how information flows right from all the different leaves of the tree, all the way down to the root. Samples of this can be found in a number of places.
In SQL tuning, you'll usually hear the word "optimizer". This is actually the area of the server of the database that has the obligation of processing precisely what the best execution plan is. The optimizer makes these kinds of decisions by going through the knowledge it's got on the content of the database. Particular servers do incorporate a Query Analyzer, that's another amongst Oracle 11g new features. An SQL statement may be easily entered in the query window and tapping Ctrl and L will execute it.
People involved in Oracle performance tuning search for methods to reduce the use of the processor. They also try to look for much better ways of utilizing available memory. What's much more important, however, is reducing disk access, which happens to be the actual bottleneck.
If you'd like to be involved in performance tuning in Oracle, you need to know about pages. A page certainly is the allocation unit of the database engine. Often, this is only a few kilobytes. Each page has a number of records on it and you ought to look at both page access and record access with regards to knowing the optimal query.
In a query plan, there are several quite primitive functions. Anybody who is actually involved in performance tuning in Oracle needs to be mindful of this. Most of these operations consist of just how to use an index, tips on how to read a full table, just how to execute a hash join as well as how to perform a nested loop for instance. Just about all of these procedures will have an output, which is their own result set. The actual inputs, however, can be either single or multiple. Inputs are attached to the output, and that's why a query plan might be graphically symbolized as a tree, which is amongst the Oracle 11g new features. This shows exactly how information flows right from all the different leaves of the tree, all the way down to the root. Samples of this can be found in a number of places.
In SQL tuning, you'll usually hear the word "optimizer". This is actually the area of the server of the database that has the obligation of processing precisely what the best execution plan is. The optimizer makes these kinds of decisions by going through the knowledge it's got on the content of the database. Particular servers do incorporate a Query Analyzer, that's another amongst Oracle 11g new features. An SQL statement may be easily entered in the query window and tapping Ctrl and L will execute it.
People involved in Oracle performance tuning search for methods to reduce the use of the processor. They also try to look for much better ways of utilizing available memory. What's much more important, however, is reducing disk access, which happens to be the actual bottleneck.
If you'd like to be involved in performance tuning in Oracle, you need to know about pages. A page certainly is the allocation unit of the database engine. Often, this is only a few kilobytes. Each page has a number of records on it and you ought to look at both page access and record access with regards to knowing the optimal query.
About the Author:
Learn more about SQL tuning. Stop by Quinn Baker's site where you can find out all about Oracle performance tuning and what it can do for you.
No comments:
Post a Comment