Performance problem with lt22

[Former Member]

I had created secondary index for table LTAP to fine tune LT27 but it decrease performance with LT22 Please replay.

Moderator message - Welcome to SCN.

But

Moderator message - Please ask a specific question. For what table did you create the index? What does the index look like? Have you run ST05 to see where the problem lays.

Edited by: Rob Burbank on Nov 19, 2009 10:22 AM

Edited by: anmol112 on Nov 19, 2009 4:35 PM

[Former Member]

Please use the ST05 for doing the SQL Trace on the program or Transcation code you are running .

it will record all the database fetch timings . as you are already aware that in one table if you create a secondary index , then it is giving an performance issue on other table . it means the select query on both the table as the same where condition or the for all entire command would hav been used . so either you need to create an index in the other performance issue table also .

But my idea would be i will see the trace , then i will go and see the select query on all the 3 table' which are affected with performance .if all 3 table select query are one of after the other then i will check the internal tabl strucuture for the 3 table's

some time same internal table strucuture ,differen strucuture would hav been used , based on that i will create the secondary index .

matrix example is :

if Custom program , try to use PRIMARY Index, if you are requirement is not set then SECONDARY Index with maximum primary keys in that .

if standard program only way is to create the SECONDARY Index , but please see the where condition for all the 3 tables and create the index.

Creating secondary index for Standarb program : there are lot of wiki's in Our SDN.

Regards,

[Former Member]

Thanks for your replay,

I had checked the SQL trace, LTAP is taking time to fetch the data, can you tell me if I am having many secondary indeces in a table, will these affect performance.

-Anmol

[Former Member]

Hi Friend ,

It is not about the many secondary index , it takes time when data selection doesn't follow any of the indexs.

so what you can do is see that trace , if it is taking time in any of the select Query ,then see the where condition and create the same sequence one more Secondary index .

so that it will reduce the performace isuse .

any select querly for the same table will search for the secondary index with its wher condition fields .if it is not having any of its sequence as primary or secondary index ... then it will be a performace issue .

so please check all the place it is following any of the index or not , if not the create one more index with that sequence .

Regards,

Edited by: Loganathan girishkumar on Nov 20, 2009 6:12 PM

[Former Member]

Answered, Clossing the threat.