| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 756.1 | No Sybase support for Rdb | TRCA03::MCMULLEN | Ken McMullen | Wed Oct 03 1990 16:46 | 14 | 
|  |     Keith,
    
    Sybase does not interface with Rdb/VMS. Just because a system is an
    "SQL compliant system" does not mean that one vendor's tools will talk
    to another vendor's relational database. 
    
    Sybase makes noise about their "Open Data Architecture", which means
    that you could hook 3gl programs to their toolset that could read and
    write to other data resource managers. But then you can do this with
    just about everone's products. The problem with this approach is that
    there is no way to co-ordinate updates (ie 2PC, data integrity) with
    the SYSBASE tools and other data resource managers.
    
    Ken
 | 
| 756.2 | Sybase Support | SAC::STEPHEN_I | Iain Stephen | Thu Oct 04 1990 10:16 | 23 | 
|  | Take an application view...
When you say "a customer who is considering the VAX/Rdb but has some existing
    	      Sybase users"
Do you know if the applications they use where written with Fastbuild or
APT workbench. 
If the Answer is Fastbuild, then something may be possible.  Fastbuild is
Sybases version of UnifAce with restricted database drivers.   UnifAce can
supply additional database drivers for the product, so you could get an 
Rdb/VMS database driver from them.  Once you have the Rdb/VMS driver, and 
creat an Rdb database, Uniface/Fastbuild can be used to move the database 
from one database system to the other.  Changing a definition in the 
Fastbuild conceptual schema tells the application to get data from the Rdb
database not the Sybase one.
In theory its a great idea...
On the other hand, if they used APT Workbench, you may be stuck with Sybase 
unless you start from scratch.
Iain.
 | 
| 756.3 | Try Sybase's OPEN Server Product | POBOX::LACEY | ACMS/Rdb, the transaction Autobahn | Mon Oct 08 1990 15:07 | 12 | 
|  |     Sybase has announced their 'OPEN Client' & 'OPEN Server' products.
    I believe you can use the OPEN Server API to write routines that utilize
    Rdb. In that way a Sybase application can access both Rdb & Sybase as
    if they were both Sybase databases. Sybase is already touting this
    functionality for access to DB2 read/write-able. 
    
    Sounds like a neat marketing idea!!, but you have to remember the 'OPEN
    Server' is not so open it uses a proprietatry API just as ACMS would
    without the application knowing whether it was utilizing Rdb, Sybase,
    RMS, ...
    
    _Paul
 |