Conference orarep::nomahs::rdb_business

152.0. "SQL*Net for Rdb7 - Media Info" by BROKE::SERRA (Rdb Engineering) Wed May 14 1997 14:12

   SQL*Net for Rdb7    MEDIA INFORMATION 
    
    -------------------------------- 
    
    Media Group: SQL*Net for Rdb Client 
    
    Part Number # of Media Label 
    
    ----------- ---------- --------------------------------- ------ 
    
    A53980-01 1 SQL*Net for Rdb7 Client Version 1.0.0.0.0 
    
    for Windows 3.1, Windows 95, Windows NT
    
    Media Group: Media Group for SQL*Net for Rdb Server 
    
    Part Number # of Media Label 
    
    ----------- ---------- --------------------------------- ------ 
    
    A53983-01 1 SQL*Net for Rdb7 Version 1.0.0.0.0 
    
    for DEC VAX OpenVMS, Digital Alpha OpenVMS 
    
    NEW AND EXISTING DOCUMENTATION INFORMATION 
    
    ----------------------------------------------------- 
    
    N = New E = Existing 
    
    Type Part Number Description 
    
    ------------------------------------------------------------------------
    
    N A53243-01 Before You Install Oracle Rdb SQL*Net for Rdb 
    
    for OpenVMS 
    
    N A53247-01 Oracle Rdb Guide to SQL*Net for Rdb 
    
    N A53248-01 Oracle Rdb A Comparison of SQL Dialects for 
    
    Oracle and Oracle Rdb 
    
    N A42343-1 Oracle Rdb7 for OpenVMS Oracle SQL/Services 
    
    Installation Guide 
    
    
    QUESTIONS AND ANSWERS
    
    Q: Are there any prerequisites for installation?
    
    A: Rdb7 is the prerequisite release (the underlying Rdb7 engine has
    several new Oracle7 functions providing the foundation for this 
    component). SQL*Net for Rdb is installed once on each server each Rdb7 
    database that will be accessed as the necessary environment must be defined
    through the emulated Oracle data dictionary views. 
    
    Q: When do I use SQL*Net for Rdb7 rather than a Transparent Gateway?
    
    A: Use the Transparent Gateway if you need to combine Rdb7 data and
    Oracle7 data. SQL*Net for Rdb does not support information sharing 
    between the two databases in this release.
    
    Q: When do I use SQL*Net for Rdb7 rather than ODBC?
    
    A: Use ODBC if you require features, such as transaction re-usability,
       not yet available with SQL*Net for Rdb7. Use SQL*Net for Rdb7 if 
       you are accessing from platforms other than Windows, or if you 
       wish to write one application that can access either Oracle7 or 
       Rdb7 as the server.
    
    Q: Are there any other limitations in this release?
    
    A: Major limitations for this release include: 
    
           Internationalization - no support for multibyte character sets
                    and message files other than U.S. 
           Rdb7 stored procedures - stored procedures and functions cannot
                    be called from PL/SQL. 
           SQL/Services universal services - only preattached database
                    services are supported and only one database attach is 
                    allowed per service. 
           SQL/Services Transaction reusable services - these are not
                    supported 
           Multisession server - Multisession server is not supported
                    because of locking differences between the two database 
                    engines. 
           No server-side PL/SQL support - this release provides client
                    convergence; server-side convergence will be addressed 
                    in the next major release. (This means that application
                    partitioning within Developer/2000 is not supported 
                    for Rdb.) 
    
    We are planning a follow-on release (planned availability this Summer,
    1997) to address internationalization and Rdb7 stored procedure support. 
    We are also planning a second major release in the Rdb8 time frame to 
    address other features and requirements. 
    
    Q: What do I sell?
    
    A: There is no charge for this component - it is enabling software!
    However, you can sell Developer/2000, Web Developer Suites, and 
    Oracle technologies using OCI.
    
    Remember, the connect itself is a server-side component for the Rdb7
    server; the client-side components do not ship with the connect - 
    those are the parts the customer purchases.
    
    
    Questions may be directed to [email protected]