|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
SAPDB Performance very low with big sql Statement
From: Danny Tramnitzke (vadus
gmx.de)
Date: Thu Jul 03 2003 - 06:38:11 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi all
I have a BIG SQL Statement, which takes more than a half hour to got the
result (so, after a half hour I stopped the process..)
I guess, to post the hole sql it self, makes not big sence, but I post the
explain output:
OWNER TABLENAME COLUMN_OR_INDEX STRATEGY PAGECOUNT O D T M
C IRAS010A INDEX SCAN 1498 *
E IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
T IRAS007A INDEX SCAN 25780 *
D IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
C IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
DBAOTI DUAL TABLE SCAN 1
A IRAS010A INDEX SCAN 1498 *
B IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
T IRAS007A INDEX SCAN 25780 *
A IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
DBAOTI DUAL TABLE SCAN 1
T IRAS007A INDEX SCAN 25780 *
O IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
DBAOTI DUAL TABLE SCAN 1
RAM TABLE SCAN 1691
PTI IRAS009A JOIN VIA RANGE OF MULTIPLE INDEXED COL.7646
PROD_NO (USED INDEX COLUMN)
FT IOTI007A JOIN VIA MULTIPLE INDEXED COLUMNS 12656
TRACK_NO (USED INDEX COLUMN)
TRACK_EXT (USED INDEX COLUMN)
CLIENT_KEY (USED INDEX COLUMN)
T IRAS007A JOIN VIA MULTIPLE INDEXED COLUMNS 25780
TRACK_NO (USED INDEX COLUMN)
TRACK_EXT (USED INDEX COLUMN)
CLIENT_KEY (USED INDEX COLUMN)
CSC01 RESULT IS COPIED , COSTVALUE IS 782116
So, it is possible to imagine the time, which sapdb needs to execute the
statement, by reading this Explain ?
It's strange, that sapdb needs so much time, because, in Sybase, this SQL
takes just a few Seconds.
Because, there might be a format error while transfert the email, I attach
a text-file with formated Output of the EXPLAIN Statement..
Best Regards,
Danny
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
OWNER TABLENAME COLUMN_OR_INDEX STRATEGY PAGECOUNT O D T M
C IRAS010A INDEX SCAN 1498 *
E IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
T IRAS007A INDEX SCAN 25780 *
D IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
C IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
DBAOTI DUAL TABLE SCAN 1
A IRAS010A INDEX SCAN 1498 *
B IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
T IRAS007A INDEX SCAN 25780 *
A IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
DBAOTI DUAL TABLE SCAN 1
T IRAS007A INDEX SCAN 25780 *
O IRAS010B JOIN VIA MULTIPLE INDEXED COLUMNS 1498
SUB_TRACK_EXT (USED INDEX COLUMN)
SUB_TRACK_NO (USED INDEX COLUMN)
DBAOTI DUAL TABLE SCAN 1
RAM TABLE SCAN 1691
PTI IRAS009A JOIN VIA RANGE OF MULTIPLE INDEXED COL. 7646
PROD_NO (USED INDEX COLUMN)
FT IOTI007A JOIN VIA MULTIPLE INDEXED COLUMNS 12656
TRACK_NO (USED INDEX COLUMN)
TRACK_EXT (USED INDEX COLUMN)
CLIENT_KEY (USED INDEX COLUMN)
T IRAS007A JOIN VIA MULTIPLE INDEXED COLUMNS 25780
TRACK_NO (USED INDEX COLUMN)
TRACK_EXT (USED INDEX COLUMN)
CLIENT_KEY (USED INDEX COLUMN)
CSC01 RESULT IS COPIED , COSTVALUE IS 782116
_______________________________________________
sapdb.general mailing list
sapdb.generallistserv.sap.com
http://listserv.sap.com/mailman/listinfo/sapdb.general
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]