Re: Migrating to Oracle on Windows

On May 21, 5:53 pm, Serge Rielau <srie..._at_ca.ibm.com> wrote:
> goooooglegro..._at_yahoo.com wrote:
> > I would have thought that this would be a common thing to do and thus
> > would have a solution that was well known among the database community
> > - so I am just looking for some help\guidance.
>
> Actually switching data servers is not common at all.
> One thumb rule that some go by is that any decision on a DBMS for a
> given app remains in place for seven years (one may argue the exact
> number but long by software standards it is).

Talk Like Yoda Day, it is! http://www.yodaspeak.co.uk/index.php

> After those seven years the app is reasonably dependent on the DBMS and
> any change is quite expensive. Hence you see some interesting vendors
> popping up like Ants (Sybase -> Oracle)or EDB (Oracle -> Postgress).
>
> The regulars in this group will be the first to tell you that an app
> should exploit the DBMS intricacies to the fullest....
>

I agree that it is not common, but it certainly is a big selling point among many app vendors.

On the other hand, when it is done, it can be a lot of work. Some people can get quite lucrative work specializing in such things. Large organizations are likely to be db-heterogenous and have a backlog of old apps that could benefit from a migration like the OP asks about. I got an unsolicited PDP job email yesterday... yeesh.

jg

--
@home.com is bogus.
"Your update subscription (customer number xxxxx-xxxx) expired on
December 31, 1969." - F-Prot