Troubleshotting Physical reads
All,
I have a query that joins 7 tables and does an 'ORDER BY' at the end to enable getting top 25 results(part of our pagination). Most of the selections happen from a partitioned table. The 'ORDER BY' even though it is on a single column(number field) is causing severe physical reads. With out the sorting, the query takes just under 2 secs, but needs almost 5 mins with the ORDER BY clause. I have used the 'run_stats' by Tom, to know that the reason is the close to 200M of physical reads that are happenning. I tried a couple of options: altering the session to use an
I have a query that joins 7 tables and does an 'ORDER BY' at the end to enable getting top 25 results(part of our pagination). Most of the selections happen from a partitioned table. The 'ORDER BY' even though it is on a single column(number field) is causing severe physical reads. With out the sorting, the query takes just under 2 secs, but needs almost 5 mins with the ORDER BY clause. I have used the 'run_stats' by Tom, to know that the reason is the close to 200M of physical reads that are happenning. I tried a couple of options: altering the session to use an
0