T.R | Title | User | Personal Name | Date | Lines |
---|
894.1 | NOVA::INGRES_TOOLS_FOR_RDB | MBALDY::LANGSTON | assimpleaspossiblebutnotsimplr | Wed Mar 20 1991 21:16 | 1 |
| Press KP7 to add the conference: NOVA::INGRES_TOOLS_FOR_RDB.
|
894.2 | SQL, not RDO | BROKE::THOMAS | | Sat Mar 23 1991 01:24 | 8 |
| The Ingres Tools for Rdb communicate with Rdb using SQL, not RDO,
not DSRI. The Ingres Tools do not run slower with Rdb than they do
with Ingres. And since Rdb is faster than Ingres, one would assume
that they run faster on Rdb.
Why would you _not_ consider selling them Rdb? If they are displeased
with the performance of the Ingres Tools, then perhaps you should sell
them a different tool kit.
|
894.3 | One Attach for many users ? | TAV02::ARIE_L | Arie Levy | Sun Mar 24 1991 12:13 | 10 |
| I'll appreciate further explanation,
INGRES ver 6 works in a Multi_server architecture.
Does it mean that by using INGRES tools for Rdb, You can have many Rdb users
Using one attach to the database, done by INGRES server ?
Thanks,
Arie Levy
|
894.4 | Dynamic SQL | TRCO01::MCMULLEN | Ken McMullen | Tue Apr 02 1991 17:46 | 21 |
| Ann,
Your statement re "Ingres Tools do not run slower with Rdb than they do
with Ingres" is a little misleading. True the Tools produce application
code that compiles and run. But in an Rdb environment they are not able
to make use of the Ingres catalogue during run time. The implementation
of the "Ingres catalogue" within the Rdb database is not the best
performer at run time. Ingres has said they have a lot of "tuning" to
do in that area.
The database calls to Rdb are via dynamic SQL, which has a little extra
overhead on the database calls. In a totally Ingres environment, the
calls are compiled and optimized before the call.
Reality also says, unless it is a large database Rdb and Ingres will
most likely perform equally. Therefore a total Ingres tools/database
verses Ingres tools/Rdb may perform a little better due to the above.
Hopefully a few cycles/IOs will not matter in most customers scenarios.
Ken M
|