Karen Hill wrote:
>>Please read Chapter 1 of Tom Kyte's "Expert Oracle Database Architecture:
>>9i and 10g Programming Techniques and Solutions" for a good discussion on
>>the reality of your database indeependence requirement.
>>
>>Your desire to stay database independent is simply going to cause your
>>customers to increase their cost. Database independence means not taking
>>advantage of the vendor's capability, which in turn means more CPU
>>cycles, and THAT means more CPU and therefore more licenses to do the
>>same job.
>
>
> Not unless you use PostgreSQL.
You mean not if they don't want support.
You mean not if they don't want robust backup and recovery ability.
You mean not if they don't care about US Federal law (SarbOx, FACTA, HIPAA)
You mean not if they don't care about European law (Basel II)
You mean if they don't need to store and retrieve TB
You mean if they don't need messaging
You mean if they don't need instrumentation for tuning
You mean if they don't need advanced security and auditing
etc. etc. etc.
Those people. Do they really BUY things?
--
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)
Received on Fri Dec 23 2005 - 11:09:47 CST
