T.R | Title | User | Personal Name | Date | Lines |
---|
680.1 | | MINDER::PICKERING | Man.United, FA Cup '90 Winners | Thu Jun 28 1990 12:13 | 9 |
| Well Rdb runtime is packaged with VMS so you only by the media &
documentation; so no price difference between it and RMS ie free. But for
Rdb development licenses..get your price book out. $4M is a bit of a
difference; how many systems is that for?
As for performance, well this can get a bit religious. Rdb engineering
would say Rdb is better, RMS engineering would say RMS is better. I
think they're much the same. With Rdb you get better data integrity,
ease-of-use, better security, better DBA facilities, blah, blah,...
|
680.2 | IBM bid? | GLDOA::RSMITH | | Thu Jun 28 1990 16:57 | 9 |
| We do not have any moles within the customer's organization, therefore
we do not know the configuration that IBM is bidding. However, I
suspect IBM is bidding the air cooled, 43xx series for the VSAM
proposal and the water cooled, (i.e. expensive environmentals) 3090
series for the DB2 version.
Thanks for your response,
Ray
|
680.3 | | NZOV07::HOWARD | NZ: Where Digital's Week Begins | Sat Jun 30 1990 10:17 | 10 |
| Why not let us know what systems you propose for your RMS solution,
and some details on what the customer wants the applications to
achieve.
RMS solutions are usually "faster" than relational database solutions
because they are generally asked to do less (no journalling,
transaction integrity etc).
Cheers, Martin
|
680.4 | Relational is future | MAIL::DUNCANG | Oracle... the one-line database | Wed Jul 04 1990 01:36 | 29 |
| I believe Rdb would be a performance winner when:
- you are running on a cluster and RMS locks are heavy
- when you need to spread a physical file (table) across many spindles
and don't want to use disk striping
- when you retrieve records using several indexes
- when you retrieve related records from separate tables (files) and
need to avoid DIO
- when you need to have flexibility in table design and the number of
fields and are likely to be making changes
I believe RMS would be a winner when:
- you did not have time to perform proper Rdb logical and physical
design
- you chose to ignore the trends in processing today which are clearly
relational
To summarize:
- Rdb is more difficult to implement due to the number of options for
tuning and placement
- When properly tuned, Rdb should be able to perform as well as, if not
better than RMS
- Rdb would put your customer in the best possible position for future
use of the data and unknown changes in the record content
(metadata)
-- gerry
|