[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ulysse::rdb_vms_competition

Title:DEC Rdb against the World
Moderator:HERON::GODFRIND
Created:Fri Jun 12 1987
Last Modified:Thu Feb 23 1995
Last Successful Update:Fri Jun 06 1997
Number of topics:1348
Total number of notes:5438

1010.0. "ORACLE SQL*FORMS -> Rdb" by AUNTB::CLARK () Wed Oct 16 1991 23:45

    I am working with a customer (same as in 1009) who is evaluating SQL*FORMS
    as an application generation tool. The customer would like whatever
    tool they select to be able to access Rdb and ORACLE databases. 
    
    The customer says that according to ORACLE, SQL$FORMS does provide
    access to Rdb.
    
    Is this true? Does anyone know how this works? Do you have to have the
    ORACLE database on the VAX to get to Rdb?
    
    Sandy Clark @CEO
    Sandy Clark @CEO
T.RTitleUserPersonal
Name		DateLines
1010.1HmmmmTYFYS::MUNNSFri Oct 18 1991 17:0626
    Oracle's SQL*Forms V2.x and V3.0 work only with Oracle databases.  V3.0
    is the most recent release (we received that version from Oracle on
    yesterday, Oct 17 !).  In fact, V3 forms actually store forms information 
    in the Oracle database.                 
    
    Either the customer is confused or Oracle is referring to a new, 
    unreleased feature or product.  If SQL*Forms did have full read/write 
    access to Rdb/VMS databases, then Oracle would lose many of their
    Oracle/VMS sites, since the cost advantages of going to Rdb/VMS
    are so significant (Oracle does not have runtime licenses).
    
    Customers of Oracle that desire their SQL*Forms applications to access 
    Rdb/VMS are rewriting their applications using an open development
    environment or are using conversion tools to assist them.  For the
    rewrites, there are a number of 4GL tools that can provide full access
    to both Oracle and Rdb/VMS.
    
    It makes sense for Oracle to do what many other 4GL development tools
    already do (access multiple database engines).  Application portability 
    is what customers are starting to believe.  An Oct 14th Digital news
    article reveals that Oracle/VMS revenues dropped from $39M in Q1 FY91 to 
    $21M Q1 FY92 (46% nosedive !)  They may be writing off VMS as Rdb/VMS is
    now the db engine of choice for VMS platforms.  In percentage of sales,
    Oracle receives 17% from VMS, 63% from UNIX.
    
    market continues to grow.
1010.2$TYFYS::MUNNSFri Oct 18 1991 17:357
    If Oracle is providing access paths to multiple databases using the
    Oracle engine as a requirement, customers will be hit with Oracle's
    famous licensing fees as well as poor performance.  The cost factor is 
    the primary reason customers are looking for non-Oracle solutions.  
    
    Have your customer figure the costs involved (licensing, maintenance)
    over 5 years, then you will no longer hear them say, "But O says..."
1010.3Many databases, as long as it's Oracle!IJSAPL::OLTHOFHenny Olthof @UTO 838-2021Wed Nov 27 1991 16:208
    SQL*Forms is a 4GL type tool that works on databases on many platforms
    using many different network protocols. As long as the database is
    ORACLE and nothing but Oracle.
    
    So SLQ*Forms, SQL*plus, SQL*@#*$%!@ do NOT WORK ON Rdb/VMS
    
    Nice salesrep, this Oracle guy,
    Henny Olthof, TP-DB Netherlands
1010.4Still no SQL*Connect for Rdb/VMSBROKE::THOMASAnne Thomas DTN 264-6094Fri Jan 17 1992 22:3111
In order for SQL*Forms to access Rdb/VMS, ORACLE would need to release 
another SQL*Connect product, a SQL*Connect for Rdb/VMS.  Thus far, ORACLE
has repeatably denied all rumors which intimate that they might be building
such a beast.

To date, Oracle has released 2 SQL*Connect products.  One provides access
to DB2 and SQL/DS, the other provides access to RMS.  

Oracle _is_ a member of the SQL Access Group, and they have developed 
SQL Access Prototypes, but they certainly don't have any production-class 
Rdb access tools based on SQL Access or SQL*Connect.