by Nina Marko » Thu, 14 Mar 2002 01:02:24
Does anybody have experince (or have heared something) with both Ingres II 2.0
and 2.5? I'll probably have to install new Ingres version. At the moment we have
Ingres II 2.0/9808.
What I know from Release notes on CA site is that 2.5 is faster and can deal
with bigger files.
I'll appreciate any comments on how happy are you with them, how robust are
they, how many bugs?
Regards,
Nina
by Nina Marko » Thu, 14 Mar 2002 02:50:23
So, you think that we will not lose much if we stay with II
2.0 ?
Nina
>>Hi, there,
>>Does anybody have experince (or have heared something) with
both Ingres II 2.0
>>and 2.5? I'll probably have to install new Ingres version.
At the moment we
>>have
>>Ingres II 2.0/9808.
>>What I know from Release notes on CA site is that 2.5 is
although I don't thinkQuote:>>with bigger files.
>>I'll appreciate any comments on how happy are you with them,
how robust are
>>they, how many bugs?
>They are pretty much even I think. There are bugs in both
versions. If you
>don't run into them they are fine. If you do, then you will
get a fix for 2.5
>but not for 2.0. I can think of no reason to avoid 2.5,
Regards,Quote:>you should get your hopes up too high for it being faster.
It might be a bit
>faster, but nothing spectacular.
>Roy Hann
><http://www.rationalcommerce.com/>Rational Commerce Ltd.
>"Ingres development, tuning, and training experts"
1. II 2.0 -> II 2.5 under Solaris 8
Hello all,
I just finished an upgrade from II 2.0/9808 to II 2.5/0006 under Solaris 8.
One important
tip for all: do an automated upgrade when the upgrade procedure asks you. in
the release
notes you will read to unload all databases and later to reload them. this
will not work in
some cases:
- The table ii_atttype has a column names system_maintained.
"system_maintained" now
is a reserved word so you can't use the reload.in script that was
generated with 2.0 unloaddb.
You can change the colum name from system_maintained to sys_maintained.
this will
reload your database.
- Two of our databases that were reloaded in this manner can't be optimized
via optimizedb -zk
- If you try not to upgrade the databases automatically and not to reload
them, just to
upgradedb them manually afterwards this will not work too.
I will keep you informed....
2. mdx problem
5. Ingres installation problem - Ingres II 2.5 on hp-ux 11
6. Universe error on SCO Openserver 5: Any ideas?
7. Upgrade question, II 2.0 -> 2.5
8. Let me know 'holdlock', please.
9. Upgrade to II 2.5 rather than 2.0 from 6.4/07
10. Ingres II 2.5 on Windows XP Pro
11. Unusual warning message from optimizedb on Ingres II 2.5
12. 64 bit architecture and Ingres II 2.5
13. Statistics question Ingres II 2.5