Conference ulysse::rdb_vms_competition

683.0. "Us against SYBASE" by SRFSUP::LANGSTON (Relational db for the nineties.) Fri Jun 29 1990 20:09

We're competing against SYBASE at a large bank headquartered in L.A.  The hot
buttons are performance, integrity, and two-phase commit between VAX DBMS and
the relational database they choose.  SYBASE has almost sold them on the "we
have the technology now to allow you, Mr. Customer, to code the 2PC yourself" 
line.

A combination of two facts is causing them to drag their feet a little on
seeing things our way:
    they have to have this done by January 1 and

    2PC for Rdb is not here yet

However, we're beginning to slowly turn them our way with VAX/VMS, motherhood
and apple pie, and fortunately we have a pretty good relationship with the
customer; a former Digital employee is their manager of systems.  

SYBASE went in there last week and did a little test that impressed the guy at
the bank who has to deliver the goods by January.  Below is a copy of a memo
obtained by our sources (the ex-Deccie gave it to the sales rep ;-) ), which
roughly outlines what the test was supposed to do.

We are going to try to duplicate the test and lay to rest their concerns about
Rdb's performance compared to SYBASE.  I know that there are a lot of things
that SYBASE could have done to make their "test" run fast.  Assuming that we
can find out what some, most, or all of those things are and neutralize any
advantage they might have, what are the things we should do, from initializing
the Rdb database disk with /NODATA_CHECK (or not?) to turning off journaling to
whatever else?


The memo:
-----------------------------------------------------
From:   yyyyy
To:     xxxxx
Subj:   SYBASE Acceptance test

         The test I wish to perform is based on the successful loading
    of xxxxxx's reporting database.  The volume requirment is for a
    minimum of 100,000 [actually turned out to be 130,00] HIREC and HLREC's.
    The test program will generically start on selected accounts' HIREC 
    processing all HIREC's for that account.  Do a transaction as defined as:
    
    
    For each HIREC do
    
    - store an FTREC using the reverse sign of HISFA and HIVVL.
          Filling the record from the data in the HIREC.
    
    - Modify the HISFA and HIVVL to zero.
    
    - For each HLREC with where the following fields are equal:
            HIACNO = HLACNO
            HICUSP = HLCUSP
            HIPICD = HLPICD
    
            - store an HTLREC using reverse sign of HLSFA and HLTXCS
                    Filling the record from the data in the HLREC.
    
            - Modify the HLSFA and HLTXCS TO ZERO
    
    - commit
    
        The average length of this transaction can not exceed 3 seconds.
    The System is ZZZZZZ and this test must be performed during the
    business day.
    
        All known software should be cover in the SYBASE license. 
    They are not to withhold any software for extra cost.
    
        I expect to receive 6 MacIntosh's with the SYBASE order.
      
----------------------
end of memo

Prior to the start of the test, SYBASE loaded the HIREC and HLREC data in 20
minutes, which impressed the customer.  Any help will be greatly appreciated;
this is a BIG deal!

Thanks,

Bruce

Cross posted in Rdb_VMS_Competition and Rdb_3.1

I was back for a class in Marlboro earlier this year and
had a discussion with the support rep for Reuters.  Reuters
picked SYBASE over Rdb because they do a lot of writes
with little update.  SYBASE has always blown us away with
write intensive benchmarks.  Try to steer the customer to
more update intensive benchmarks and have them evaluate
referential integrity features, degree 3 read consistency and
journalling features.

I saw a few demos at DECworld that did simultaneous updates
to Rdb and DBMS using DECdtm.  

Larry