‎2007 Dec 08 7:29 PM
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.
‎2007 Dec 08 9:30 PM
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
‎2007 Dec 09 12:16 PM
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