Hi,
we're wondering about the heavy load our maxdb produces.
After some time of investigation we found out that the database produces
a lot of table scans.
Why we are wondering is, that our currently running 7.3.0.46 doesn't produce
table scans, furthermore this version uses the created indices (and MaxDB
doesn't...).
An "explain" of a test statement shows us a completely different behaviour of
statement execution. The costvalue from MaxDB is 10-times the value from
the 7.3.0.46 :-((
This behaviour is hardware-independant (we tested different cases), and we
wanted to know if there is a possibility to force MaxDB using indices for
reducing load.
The explain outputs of our test-statement for both cases are attached.
Perhaps problems with multiple-column indices ???
We want to upgrade our currently running database version, so we need help,
because this heavy load isn't that funny...
thanks a lot
-GERD-
SD TABLE SCAN 1112
D DELIVERY_ID JOIN VIA KEY COLUMN 1223
S SLOT_ID JOIN VIA KEY COLUMN 7180
T TIME_ID JOIN VIA KEY COLUMN 8
G GATE_ID JOIN VIA KEY COLUMN 5
RESULT IS COPIED , COSTVALUE IS 17471
S DELIVERY_DAY EQUAL CONDITION FOR INDEXED COLUMN 4506
T TIME_ID JOIN VIA KEY COLUMN 8
SD TAB_TISLOT_SLOT_DELIVERY_SK3 JOIN VIA RANGE OF MULTIPLE INDEXED
COL. 1053
SLOT_ID (USED INDEX COLUMN)
D DELIVERY_ID JOIN VIA KEY COLUMN 1195
G GATE_ID JOIN VIA KEY COLUMN 2
TISYS RESULT IS COPIED , COSTVALUE IS 1726
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
