| business
intelligence |
| MODEL
clause: |
|
|
|
 |
This
powerful new clause allows you to perform complex computations
and predictions based on current data without the need for
excessive joining and UNION clauses. It’s also OLAP
compliant and can be used with Oracle OLAP features. |
|
| Partitioning
Enhancements: |
|
|
|
| You
can now partition Index Organised Tables (IOTs). Hash partitioned
global indexes are also available. |
|
| Recovery
through Resetlogs: |
|
|
|
| This
is now possible using an additional tag in the archive_log_format
init.ora parameter. The new %r format command shows which
incarnation of the database the log refers to as well as
the thread and sequence number. |
|
| Asynchronous
Change Data Capture: |
|
|
|
| Change
Data Capture was introduced in Oracle 9i and is a powerful
tool for updating your data warehouse from the source databases.
10g introduces Asynchronous capture, meaning changes captured
in the redo logs can be propagated to the warehouse via archive
logging, and then applied to the warehouse using Oracle Streams
technology. |
|
| Query
Re-write Enhancements: |
|
|
|
| The
new optimizer hint “rewrite_or_error” can be
used to cause statements to fail if they are not re-written. |
|
| Materialized
View Enhancements: |
|
|
|
| Partition
Change Tracking, introduced in Oracle 9i for range and range-hash
partitioned tables, can now be used for all partitioning
types. This means that each partition tracks its own changes
via materialized view logs and uses the details for a fast
refresh. Hierarchical materialized views can now be automatically
refreshed in the proper order using DBMS_MVIEW. You can also
build materialized views that depend on other views using
the “build deferred” clause and let them later
be populated via the refresh procedure. As part of the Advisor
Framework, the new materialized view advisor (DBMS_ADVISOR.TUNE_MVIEW)
has been created to help tune materialized views. |
|
| MERGE
Statement Improvements: |
|
|
|
|
It
is no longer necessary to include both the INSERT and UPDATE
clauses, only one is needed and Oracle can work out the rest.
There is now an optional DELETE clause that can delete rows
according to certain criteria. You can now perform conditional
inserts using a new WHERE clause. |
|
|
|
|
|
|
|
|
|
| |
<<
previous page |
|
next
page >> |
|