Increase Oracle 11g Performance with Native Compilation
Because natively compiled code in Oracle doesn’t need to be interpreted at runtime, it may execute faster. However, performance gains depend on several factors. Learn more.
Read MoreMost Popular Performance Tuning
Use Named Parameters in SQL Function Calls in Oracle 11g
Named notationis the preferred method for passing parameters to subroutines in Oracle. With 11g, you can extend this to SQL statements to yield consistency across the entire code base.
Read MoreTuning Distributed Queries in Oracle
When distributed queries can’t be avoided, use IN clauses, set operators such as UNION and MINUS, and use everything else you can to reduce the network traffic between database nodes. Learn more.
Read MoreChanges to the Oracle 11g Optimizer That Affect Tuning
Learn about some signiticant changes to the Oracle 11g optimzer that can affect SQL query tuning.
Read MoreUsing the EXISTS Function and the Nested Subquery in Oracle
It’s generally best to use the EXISTS function in Oracle instead of the IN function. Learn more.
Read MoreAbout Oracle Function-based Indexes
Function-based indexes in Oracle allow you to create an index based on a function or expression. Learn how this can impact performance.
Read MoreWhy Oracle Indexes Sometimes Get Suppressed
A modification of the column side of a WHERE clause in Oracle can result in index suppresseion. Learn a few alternatives for writing the query that do not modify the indexed column.
Read MoreUnderstand the Oracle Index Merge
In Oracle 11g you can merge two separate indexes and use the result of the indexes instead of going to the table from one of the indexes, which can speed performance. Learn more.
Read MoreCaching a Table in Memory for Oracle
Caching a small, often-used table into Oracle memory ensures that the data isnt pushed out of memory by other data, but can have unexpected results. Learn more.
Read MoreMaking the Oracle Query “Magically” Faster
When a query is run multiple times in succession, it becomes faster because the data is cached in memory. This can make the query seem faster when it’s not. Learn why.
Read MoreHow is AUTOTRACE Different from EXPLAIN PLAN?
The Oracle command AUTOTRACE executes the query (in the way TRACE does) and automatically queries the plan table, and the EXPLAIN PLAN command does neither. Learn more.
Read MoreTop 25 Oracle Initialization Parameters
See one expert’s list of the 25 most important Oracle initialization parameters, in order of importance.
Read More