Solved: Buffering a Table View

kmoore007 · ‎02-10-2005

We are trying to boost the performance of a table join in a custom program. I created a table view to see if the performance was any better than coding the join in the program. It was not really any better. Then, I played around with the table buffering a bit. When I set the table buffering to Generic with 3 fields, the program ran over 50% faster. Is it a bad thing to turn on the buffer for a table view? The tables joined are MKPF and MSEG.

Former Member · ‎02-10-2005

Hi Kenneth,

I don't know in what kind of company you are working, but the table you are referring to will normally be updated very regularly (material documents). In that case it doesn't make too much sense to turn on buffering as the buffer will be invalidated and refreshed very often.

Perhaps creating a suitable index will be more efficient?

Regards,

John.

Former Member · ‎02-10-2005

Hi Kenneth,

I don't know in what kind of company you are working, but the table you are referring to will normally be updated very regularly (material documents). In that case it doesn't make too much sense to turn on buffering as the buffer will be invalidated and refreshed very often.

Perhaps creating a suitable index will be more efficient?

Regards,

John.

kmoore007 · ‎02-10-2005

Can you create an index on a view?

Message was edited by: Kenneth Moore

Former Member · ‎02-10-2005

No you can't. What I ment was that your create suitable indices on the tables to have a better performance on the join in your program. But that depends on the selections you are using. If the join now runs over the primary keys it doesn't make any sense to create indices.

Regards,

John.

former_member214131 · ‎02-10-2005

Hello,

I am not sure whether Secondary Indexes BSID, BSAD, BSIK, BSAK, BSIK would help you.

I am not sure of the Secondary Index w.r.t Material Movenents.

Regards, Murugesh AS

Message was edited by: Murugesh Arcot