[Info-vax] Final Orace release on VMS.
Jan-Erik Söderholm
jan-erik.soderholm at telia.com
Thu Nov 12 11:19:11 EST 2020
Den 2020-11-12 kl. 17:05, skrev Arne Vajhøj:
> On 10/28/2020 9:59 AM, Phillip Helbig (undress to reply) wrote:
>> In article <rnbs20$on2$1 at panix2.panix.com>, kludge at panix.com (Scott
>> Dorsey) writes:
>>> Phillip Helbig (undress to reply) <helbig at asclothestro.multivax.de> wrote:
>>>> What fraction of paying VMS customers use Oracle "classic" (which is
>>>> what the announcement is about)? What fraction use Rdb? What fraction
>>>> use some other database? What fraction use no database (not counting
>>>> RMS)?
>>>
>>> Probably not many use Oracle Classic. However, if there is any chance of
>>> expanding the customer base at all and get new people to use VMS, having
>>> support for Oracle is a big, big deal. There are a lot of people using
>>> Oracle on their back end systems.
>>
>> Big users of Oracle Classic probably have an application very tied to
>> the database. There isn't a huge advantage for them moving to VMS. My
>> guess is that, among paying customers, more than half use Rdb and less
>> than 1% Oracle Classic.
>
> Rdb is undoubtedly the most important among those using VMS today.
>
> But VMS should hopefully grow beyond who are using VMS today.
>
> For a certain market segment then Oracle DB (Oracle classic) is
> very important.
>
> But:
> 1) Oracle may be difficult to persuade to change strategy (they are
> a huge company and VSI is a small company).
> 2) There are other market segments than those willing to pay
> a 5 digit dollar amount per core for database licenses.
>
> Available relational databases on VMS include:
> * Rdb
> * MySQL/MariaDB
> * SQlite
> * Mimer
> * HSQLDB
> * H2
> * Derby
>
> Arne
>
Seems as the response from Oracle is to run your applications as
usual using the client kit, but have the server on another platform.
More information about the Info-vax
mailing list