HP3000-L Archives

March 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jerry Fochtman <[log in to unmask]>
Reply To:
Jerry Fochtman <[log in to unmask]>
Date:
Thu, 4 Mar 1999 10:30:07 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (79 lines)
At 12:13 PM 3/2/99 -0800, Shawn Gordon wrote:
/snip
>Disc seems to spend much more time and
>resource on Omnidex than Bradmark does on Superdex (I can't support this,
>just an observation).

I've been out for a few days, but wanted to respond to this prior note.

On one hand I'm a bit puzzled by this perception, while on the other
hand, I can understand it given that we don't brag a lot about some of
the things we do for the user community.

Specifically, we've taken the lead in progressing a number of items in the
recent past which have potentially benefited users of both TPI products:

    1) SUPERDEX was the first TPI product to announce/provide support
       for concurrent b-tree and TPI indexes in the same database.
    2) Bradmark staff worked with HP engineers in resolving the issues
       whereby the SQL optimizer was not receiving the proper
       statistical values so as to properly and consistently consider
       TPI indexes when determining the appropriate path to use for
       a searches.
    3) Our staff also worked with HP engineers in the blending of both
       b-tree and TPI indexes for consideration of the SQL optimizer.
    4) Bradmark initiated the TPI interface design changes to provide
       performance improvements when the TPI index was not needed for
       the specific search path (new TPI-Toggling feature of IMAGE).
       We were the only TPI vendor to participate in the design meetings
       for this feature.
    5) We've also been working directly with HP-Roseville to address a
       number of the TPI-related problems in QUERY.

HP's position is to provide TPI-related features/fixes that are available
to both Bradmark and DISC.  So while we work on these issues for the benefit
of our customers, our competitor and their customers may also benefit from our
efforts as well.  Perhaps to address the perception that there has been
little work done for SUPERDEX customers recently we should be more public
about
our involvement in various issues when they are released to the public and
we're somewhat released from talking about them due to our NDAs with HP...


<plug-product specific items>

We're currently working on a number of features for an upcoming
release of SUPERDEX.  Some of the major enhancements include:

    -) Performance enhancements in (re)building indexes keys for
       a database.
    -) Integration of the same technology we developed for DBGeneral
       which removes the 4GB file limitation issues that occur when
       managing the large data volumes contained in the many jumbo
       database environments in use today.  This also includes the
       ability to efficiently sort > 4GB of index data, which can
       easily occur with these large database environments.

Included are a number of other minor defect repairs as well.  No
target date for BETA availability or general release has been set
yet, although it will probably be sometime in the 2H99.

</plug>

/jf
                              _\\///_
                             (' o-o ')
___________________________ooOo_( )_OOoo____________________________________

                       Thursday, March 4th

          Today in 1789 - 1st Congress under the U.S. Constitution
                          convened in NYC.
                   1791 - Vermont becae\me the 14th state.

___________________________________Oooo_____________________________________
                            oooO  (    )
                           (    )  )  /
                            \  (   (_/
                             \_)

ATOM RSS1 RSS2