Re: Oracle licence question

From: HansF <News.Hans_at_telus.net>
Date: Sun, 26 Feb 2006 18:04:29 GMT
Message-Id: <pan.2006.02.26.18.04.25.9187@telus.net>

On Sun, 26 Feb 2006 07:12:50 -0500, Serge Rielau wrote:

> HansF wrote:

>> On Sat, 25 Feb 2006 22:25:02 +0000, Tony Rogerson wrote:
>> 
>> 
>>>What you mean - they use portable SQL as definied by the ANSI SQL standard, 
>>>something Oracle doesn't do very well! Come on guys, catch up!! Talk about 
>>>MS locking people in - LOL!
>> 
>> 
>> I am specifically saying that vendor lockin is a good thing.  Accept what
>> is being offered and go with it.  Then, in 3 years time, when replacing
>> the system, look at what is the right tool at that time.

> Hans,
>
> Hang on..., have you seen many shops that actually switch an app after
> those three years (from or to Oracle, doesn't matter)? The moment the
> application logic (which includes procedures) has committed to the misc.
> features of a given product migration costs skyrocket.
> Typically this leads to an interesting rift between those in control of
> the money and the DBAs.

What I have seen is shops switching applications in 3 years - or (as Frank points out) 5 to 7 years. My observation around this is:

switch because of changes in functionality
switch vendors, often to one with different infrastructure experience (we've built this amazing thing in DB2 or SQL Server or Oracle)
the shop often wants it rewritten to meet the shop's "standard"
we use DB2, you have to make it available in DB2 even though it was written for Oracle
the reason is the administrators (database, system,network)
therefore, to appease the administrators we will accept an inferior port of to retain the apparent improvement in functionality,
unfortunately, the inferior port tends to have performance issues which leads to early review of replacement strategy.

And yes, I have seen shops switch vendors 'on a dime' and commit to the vendor extensions - when there is a management endorsed exit strategy.

It means the team is committed to working on that project, from initial development through retirement, for the duration. It means using true cost techniques that include Capital Expenses as well as Operation Expenses over the lifetime. And it means measuring the return on investment and using [part of] the savings that result from the return as capital for the next project rather than sluffing it to the general profit pool.

-- 
Hans Forbrich                           
Canada-wide Oracle training and consulting
mailto: Fuzzy.GreyBeard_at_gmail.com   
*** Top posting [replies] guarantees I won't respond. ***

Received on Sun Feb 26 2006 - 12:04:29 CST