Does anyone know what the big ORCL database features are really
intended to support OLAP or reporting requirements... so far I
have:
* Query re-write
* Materialized Views
* Bitmap Indexing
* Read Consistency – a previous pilot was required to use NSK "READ
UNCOMMITTED" to get any sort of viable performance, which implies
dirty reads (typically handled with rollback segments in Oracle)
* Data concurrency: Readers don't block readers, readers don't block
writers, writers don't block readers.
* Rollback - undo any uncommitted changes made by a transaction. The
transaction is ended.
Are there others I should consider ?
Thanks,
Jack
intended to support OLAP or reporting requirements... so far I
have:
* Query re-write
* Materialized Views
* Bitmap Indexing
* Read Consistency – a previous pilot was required to use NSK "READ
UNCOMMITTED" to get any sort of viable performance, which implies
dirty reads (typically handled with rollback segments in Oracle)
* Data concurrency: Readers don't block readers, readers don't block
writers, writers don't block readers.
* Rollback - undo any uncommitted changes made by a transaction. The
transaction is ended.
Are there others I should consider ?
Thanks,
Jack
Comment