| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 1111.1 | A couple of options to consider to start with | BROKE::ABUGOV |  | Wed Jan 08 1997 10:46 | 32 | 
|  |     
    Hi Kevin,
    
    If by replication you mean do changes only types of transfers from Rdb to 
    SQL Server, Rdb Replication Option supports those types of transfers,
    but only when installed on the same system the Rdb database is
    installed on.  The Replication Option allows you to schedule those
    transfers and when used with the Rdb transparent gateway to PC Data
    allows the transfer of the changed data to a SQL Server database.
    
    If you can't install anything on the VAX VMS machine then there are
    other options, but they require full table copies to the sql server
    database to keep the databases in sync, which may or may not fit your
    requirements.  You can install the Rdb transparent gateway to PC dataon
    the ALPHA machine and using interactive SQL connect both to the Rdb
    database and the SQL server database (using the pc data gateway) and do
    a INSERT INTO SQLSERVER.TABLE (SELECT * FROM RDB.TABLE);
    
    If there is a tremendous amount of data this might not work if there
    are time requirements and/or there isn't much memory to work with.
    
    You could also use the Replication Option to accomplish the same thing,
    but in this case it would be copy management as opposed to replication
    because the replication option will be installed remote from the Rdb
    database.  You would still get the benefits of being able to scheduled
    or on demand transfers.
    
    Hope this helps,
    
    Dan
    
    Hope this helps
 | 
| 1111.2 |  | ORAREP::JGODCL::BOWEN | Father RABBIT? | Wed Jan 08 1997 10:59 | 16 | 
|  |     Hi Dan, thanks for replying.
    
    My problem is that I'm not able to even install the PC DATA gateway
    client on the remote machine, unless I'm missing something the RDB
    database requires this.
    
    I have the server software running happily under FX!32 on the ALPHA!
    
    I've tried using MS-ACCESS as a bridge but as it runs under 16bit
    emulation like the VB it keeps running out of resources.
    
    Any other ideas are most welcome, it seems silly to me that I have
    this great ALPHA machine which spends all it's time waiting for the
    ODBC link to a slow VAX.
    
    Kevin
 | 
| 1111.3 | my mistake - solutions in this space are futures for us... | BROKE::ABUGOV |  | Wed Jan 08 1997 11:11 | 13 | 
|  |     
    Hi Kevin,
    
    Thanks, I didn't look carefully enough to note that your ALPHA machine
    was running NT and not VMS.
    
    I can't think of anything off the top of my head to help you with this
    problem today.  How far out in the future will this problem hit a
    critical stage?  We are working on stuff that could help in the
    semi-near future but I can't talk about it here...
    
    Dan
    
 | 
| 1111.4 |  | ORAREP::JGODCL::BOWEN | Father RABBIT? | Wed Jan 08 1997 11:22 | 12 | 
|  |     Blimey, real time noting...
    
    It's sorta a major problem for us currently, it's looking as if we'll
    have to install an INTEL box to act as a feeder.
    
    SQL Server on both and a VB4 program to load the Intel version which
    then pushes the data across to the Alpha.
    
    Mind you, considering we're using brand new and Beta stuff anyway we
    might be interested in becoming a test site for you...
    
    Kevin
 |