Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Is it Buffering?

Former Member
0 Likes
443

What is that, that is specific to the d/b table <b>COEP</b>, that a <b>SELECT</b> query in a report on this table consumes more time when it is run for the first time, however in the subsequent runs it doesn't even consume half of the time of its first run.

2 REPLIES 2
Read only

Former Member
0 Likes
425

Hi Ratan,

Use secondary indexes

The first index key fields LEDNR OBJNR GJAHR in your where clause which will give fast access to the required data.

Regards,

Satish

Read only

Former Member
0 Likes
425

Hi,

This is not exactly buffering. Actually what happens is that when you execute a query on any Data Base table then data selected from the table is kept in Cache Memory.

So when you execute a query on the same table again, then the data is taken from the Cache instead of data base table and hence it is faster.

This Cache is present till your session lasts. If you log off and login again then the time taken by two queries should be same.

Hope this clarifies your doubt. Please revert back if you need some more details on this.

Regards,

Lalit Kabra