Peter Weaver wrote:
> Neil Rieck wrote:
>
>><bob@[EMAIL PROTECTED]
> wrote in message
>>news:1109550872.067891.88350@[EMAIL PROTECTED]
>>
>>>Oracle would create a band of very unhappy customers if they tried
>>>to eol rdb
>>>
>>
>>The following interesting Oracle RDB points were mentioned at the
>>seminar:
>>...
>
>
> One other point from Norman's session that I recall is that on a slide
> he quoted Larry Ellison as saying that the way Oracle treated the RDB
> customers is a good example of how to treat customers of products a
> company buys. So I do not think there would be anyway he would EOL RDB
> after making a comment like that. Unfortunately I did not write down the
> exact quote since I figured I would get it on the slides later.
>
Oracle Praised By Thousands of Satisfied Rdb Customers
http://www.oracle.com/cor****ate/press/2337269.html
Nine Years Later - PDF
http://www.oracle.com/peoplesoft/Rdb_CaseStudyE.pdf
An Oracle Rdb-centric VMS TUD Tidbit
http://www.shannonknowshpc.com/stories.php?story=04/10/10/1936825
Oracle Rdb Statement of Direction
http://www.oracle.com/technology/products/rdb/htdocs/rdb7/rdb_statement_of_direction.html
The above shows there is plenty of collateral stating Oracle's
commitment to Rdb. I would say it is also partly due the continual
industry-leading innovation of its development team and quick new
feature release cycle despite having 3 development trees (7.0, 7.1 and
7.2). The Oracle Classic team has over 90 platforms to contend with
providing (in many aspects) a lowest-common denominator functionality
(Oracle Classic integration of the DLM on OpenVMS is an example where
this has not been the case). But Oracle Classic has a completely
different DB engine model, and has not yet been able incor****ate (or
make as good use of) many of the features and advantages developed
originally and often exclusively for Rdb. Some features were mostly
unnoticed by the public for many years before they became buzzwords for
competing products.
- Snapshot coordination of serialized transaction data
- Cost-Based Optimization
- precompiled optimized queries
- optimizer hints
- BLOBs (segmented strings) since 1984 (became buzzword c.a. 1990)
- bit-mapped indices
- latches (ultra-efficient locking)
- BLASTs used for efficient SW-interrupt-based resource coordination
- pseudo-ranked indices
- transaction- and quiet point-aware on line backup utility
- true fully-shared clustering and DLM integration
- cluster-aware rollback resolution
- true default "serializable read transaction isolation" without
needing an additional TP Monitor front-end, despite and a
necessary consequence of Rdb's ultra-scalable direct per-process
DB access model (compare Oracle Classic's served data
resource bubble model).
- log-based (AIJ) ultra-low transaction overhead Hot-Standby
database capability
- log-mining (AIJ) transaction replication interface
and more...
Rdb has also always been at the forefront of implementing SQL standards,
going far beyond the basic "Entry-Level" SQL Standards Compliance of
almost all other SQL products.
Cheers!
K.C.
