Performance problems after migration to MaxDB

Zuylen, G. van GvZuylen at
Fri Feb 2 11:05:37 MET 2007

Hello Christoph,

First of all, thanks for your reaction.
That's where we afraid for, this takes a long time to optimise. Indices on big tables must be created during downtime. The system is used in a hospital so the system is needed 7x 24 hrs.
But the good news is that this looks normal, and it seems that we don't have a technical DB problem.

Best regards,

Gert van Zuylen

-----Oorspronkelijk bericht-----
Van: Pertzsch, Christoph [mailto:christoph.pertzsch at] 
Verzonden: vrijdag 2 februari 2007 10:46
Aan: linux.general at
Onderwerp: AW: Performance problems after migration to MaxDB

Hi Gert,

we have seen these issues too after a migration from MSSQL -> MAXDB.

One Reason is: Oracle/MSSQL databases are optimizing ongoing database
requests due to there statistics of past requests... So, if you have
a table without secondary indizies for requests oracle will do this
"magically" in background to speedup the requests.
For MaxDB you have to create secondary indizies for tables, where you
monitor bad performed requests. Indizies have to create in this way,
like select condition is stated in ABAP.
For Select * FOR ALL ENTRIES in itab you have to analyse, which
fields are in the itab for create a good 2nd index.

Best regards,


Christoph Pertzsch | christoph.pertzsch at    | Telefon: +49 177 3882189

-----Ursprüngliche Nachricht-----
Von: linux.general-bounces at [mailto:linux.general-bounces at] Im Auftrag von Zuylen, G. van
Gesendet: Freitag, 2. Februar 2007 10:23
An: linux.general at
Betreff: Performance problems after migration to MaxDB
Wichtigkeit: Hoch



After an migration from Oracle 8.1.7 to MaxDB 7.6.01-10 (running on Suse SLES9 SP3 x86-64) we have serious performance problems.

Selects which are done on views and joins are performing very bad, as before on the Oracle database. Also selections with the statement SELECT * FROM <tabel> ALL ENTRIES IN i_tab are bad also.


Is there anyone who has some experience with migrations to MaxDB or recognizes this problem. And most important, how this was solved. 


With thanks in advance.


Best regards,


Gert van Zuylen

More information about the linux.general mailing list