01.09.2016 Views

Beginning Oracle Database 11g Administration From Novice to Professional

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

148<br />

CHAPTER 7 PHYSICAL DATABASE DESIGN<br />

<br />

<strong>to</strong> each s<strong>to</strong>rage pool using some criterion. The partitioning methods provided by<br />

<strong>Oracle</strong> include list partitioning, range partitioning, interval partitioning, reference<br />

partitioning, hash partitioning, and composite partitioning.<br />

<br />

in the same way as its table. Local indexes are most suitable when the query specifies<br />

the partitioning criterion; they also promote partition independence. Global<br />

indexes are most suitable when the query does not specify the partitioning criterion.<br />

A global index may or may not be partitioned and can even have a different<br />

partition scheme than its table.<br />

Denormalized tables and materialized views can be used <strong>to</strong> improve the efficiency<br />

of Join operations. <strong>Oracle</strong> au<strong>to</strong>matically modifies the data in a materialized view<br />

whenever the data in the underlying tables is modified. The optimizer silently<br />

rewrites queries and incorporates materialized views if possible. Materialized views<br />

can also be used <strong>to</strong> aggregate information or <strong>to</strong> synchronize satellite databases.<br />

Hash clusters provide quick access without the need for an index (if the value of<br />

the clustering key is specified in the SQL query). They improve the efficiency of the<br />

memory cache (and consequently of Join operations) because data from related<br />

tables can be s<strong>to</strong>red in the same data blocks.<br />

Exercises<br />

<br />

<strong>Oracle</strong> <strong>Database</strong> <strong>11g</strong> Java Developer’s Guide. Construct SQL language commands<br />

<strong>to</strong> create a suitable set of indexes on the , , , and <br />

tables.<br />

clause of the or <br />

commands <strong>to</strong> track whether your indexes are being used by the query optimizer.<br />

Where is the information s<strong>to</strong>red? Is it advisable <strong>to</strong> moni<strong>to</strong>r usage continuously? How<br />

would you s<strong>to</strong>p moni<strong>to</strong>ring index usage?<br />

<br />

SQL Access Advisor in the example in this chapter?<br />

<br />

Do indexes provide any advantage if the tables are very small?<br />

<br />

Organized Tables not invalidated if a DML operation causes rows <strong>to</strong> move?

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!