| Title: | DEC RdbExpert for OpenVMS |
| Notice: | RdbExpert V2.1A is now available - See note 2.4 |
| Moderator: | OOTOOL::CRAIG |
| Created: | Fri Jul 10 1992 |
| Last Modified: | Tue Jun 03 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 755 |
| Total number of notes: | 2761 |
Is there a cut-off for how old a version of Rdb one should
REALLY use with the latest, or any particular version of Expert ?
At some point I assume it could recommend actions that
aren't supported under an older version. If so, do we
document this restriction ?
I assume that there is one logical model of the optimizer
in Expert that always trails the current server release
by some months. In general, even if the optimizer model
is monolithic and can't differentiate between server
releases that for what it does the recommendations would
largely apply to prior releases anyway. A good index is
pretty much going to be a good index no matter what
version of the server you're using.
We document minimum OpenVMS, Rdb, and DECwindows Motif
versions for use with the product in the installation
guide, but especially in terms of differences in SQL
that we have to parse and what not this is going to
cause needless frustration and perhaps various other
problems or inaccuracies. It would help if Expert
coded for this kind of case by doing things like
ignoring the SQL it didn't need like triggers and
what not (which is bothersome even when using the
most recent releases). Do we really go back and run
regression testing under 4.0-2 for example ?
I know the optimizer logic has got to trail the server,
but let's just say I'm increasingly uncomfortable
with what we document as supported versions, especially
when I have to defend it to customers when I'm asking
them to edit things out of their SQL as a workaround.
This makes me wonder about what might be going on or
lurking in the rest of the code. I'd at least
feel better if what we documented as being the
minimum releases used newer releases, even if it
worked okay for the more intrepid.
Informed opinions appreciated.
Thanks,
rcs
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 729.1 | OOTOOL::GUAY | Oracle Expert, 1-2499 | Fri Feb 07 1997 15:39 | 31 | |
Hi Richard, In the past, we have run regression tests from Rdb 4.0-2 and upward. We have disks that are chuck full of regression test data for each server release as well as for each OS difference (AXP and VAX). We've started to move away from some of the earlier releases, such as 4.0-2, as officially supported releases. I'm not sure if you noticed, but in the latest kit the versions were moving upward. I think the officially supported releases are 6.0 and greater, if I remember correctly. Sheri will correct me if I'm wrong! Things like triggers, etc. are needed in the current approach in order to create the complete database from scratch. Most users, expecially for production databases, don't recreate their databases from scratch using the implement scripts anyway. We are moving to more of an alter approach versus a recreate the world. In the meantime, you can do things now to make Expert work more as you'd like. There is an RDBX_EXTRACT.COM file in RDBX_LIBRARY: which is used to extract the schema definition through RMU. If you edit the file and add appropriate qualfiers to not extract triggers, protections, etc., Expert will work more along the lines that you are suggesting. Of course, Expert will not be able to create a full script if this is done, but you could then set unload_style in the ini file to 2, which will cause Expert to create an import/export script for you instead, if you really need to recreate the complete db. Well, enough rambling. I hope this answers all your questions, todd | |||||
| 729.2 | Is V3.1 the latest version ?! | NOMAHS::SECRIST | Rdb WWS; [email protected] | Fri Feb 07 1997 16:39 | 27 |
; I'm not sure if you noticed, but in the latest kit the
; versions were moving upward. I think the officially
; supported releases are 6.0 and greater, if I remember
; correctly. Sheri will correct me if I'm wrong!
Is 3.1 the latest kit ? Both the installation guide and
release notes indicate 4.0-2 and 4.0 as being supported,
respectively.
; Things like triggers, etc. are needed in the current approach in
; order to create the complete database from scratch. Most users,
Whoops -- I should have thought of that ! I just never used it
that way ;-)
; In the meantime, you can do things now to make Expert work more
; as you'd like. There is an RDBX_EXTRACT.COM file in RDBX_LIBRARY:
A wonderful tip -- thanks !
Have a great weekend !
Regards,
rcs
| |||||
| 729.3 | OOTOOL::GUAY | Oracle Expert, 1-2499 | Tue Feb 11 1997 11:18 | 8 | |
I think the spreadsheet was put together just after 3.1 was released. The installation guide and the release notes will be updated in 3.2 to use more current versions. thanks, todd | |||||