T.R | Title | User | Personal Name | Date | Lines |
---|
159.1 | Error in Copying Report | WLW::SHUCKTIS | | Thu Jul 14 1988 19:59 | 10 |
| I attempted to copy this report, however, I keep getting an error
saying inappropriate device type or name.
I'd like to review this report. We are currently competing with
INGRES at GE Aircraft Engines.
Do you have any information on INGRES V6.0? How difficult is
it do convert from INGRES V5.0 to V6.0?
Any assistance with this matter is greatly appreciated.
|
159.2 | Check node address | NOVA::HILLSON | | Fri Jul 15 1988 17:54 | 9 |
| The node address for BANZAI may need to be updated in your Decnet database.
The node address for BANZAI is 31.627
There are some references to INGRES V6.0 features, and areas that are
being changed. I tried to include these as I heard about them, however
I am sure that it is in no way complete. I don't know how difficult it is
to convert from V5.0 to V6.0.
Susan
|
159.3 | INGRES on VAXCluster | BANZAI::HILLSON | | Thu Aug 11 1988 17:36 | 52 |
| The following is a note from Rdb Notes conference answered here.
<<< BANZAI::$111$DUA0:[NOTES$LIBRARY]RDB.NOTE;1 >>>
-< VAX Rdb/VMS >-
================================================================================
Note 16.1 INGRES/Rdb Comparison 1 of 1
MUCXEE::EISELE "I do it with ACMS....." 24 lines 2-AUG-1988 08:08
-< Good Job >-
--------------------------------------------------------------------------------
Thank you very much you three.
Good job; useful Information.
one comment:
I would like to see a special Chapter about the VAXCluster(non)-
functinality of INGRES.
Try out and describe the behaviour of this product:
- a node fails from which a transaction is active
- AIJ in a VAXCluster
This one of the important arguments in a presales situation.
RTI tells the customer that INGRES fully supports VAXCluster.
Question:
will this document be update, with the release of new versions of
Rdb/VMS and/or INGRES.
R�diger
--------------------------------------------------------------
I am unable to try out the behavior of a node failure on a VAXCluster
as our license is for a single CPU only. However, it is my understanding
that if one node fails all users of the database on the other nodes are
no longer able to use the database until the database is manually restored
using the RESTOREDB utility. Any user may run RESTOREDB. This process will
be changing in V6.0 of INGRES.
After image journaling is fully supported across VAXClusters.
We do have plans to update the report when Version 6.0 of INGRES is released,
as well as do functionality testing of other competitive products.
Susan
|
159.4 | is this report still there? | DEMOAX::SOLOMON | Marc Solomon - Northeast Volume Sales Support | Tue Dec 13 1988 23:53 | 9 |
| re: .0
hello. is this report still available? i'm getting 'directory
not found'
i'm also interested to know if there are any comparisons between
Ingres and DEC's 4GL tools (ie, RALLY)
thanks for any input
|
159.5 | use USD04: disk | NOVA::MAHLER | Andy Mahler | Wed Dec 14 1988 19:16 | 6 |
| Try looking in
BANZAI::USD04:[HILLSON.PUBLIC]INGRES_REPORT.LN03
BANZAI::USD04:[HILLSON.PUBLIC]INGRES_REPORT.POST
Susan moved to a different disk since the report was published.
|