Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

How to Reduce the Logical Reads, to imporve the Performance of the Query Expand / Collapse
Author
Message
Posted Wednesday, February 8, 2012 3:41 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 12:39 PM
Points: 44,730, Visits: 42,599
Dinesh Babu Verma (2/8/2012)

In case no data in data cache, the physical read will be equal to number of logical read.


Not necessarily, because a query could request the same page more than once. If the page doesn't start in cache, the first will be a physical read, the others will not.

Buffer Cash Hit Ratio
Buffer hit ratio will be calculated based on these two kinds of read as the following formula: (logical reads – physical reads)/logical read * 100%. The high buffer hit ratio (if possible to near 100%) indicates good database performance on SQL Server level. So use information from physical read and buffer hit ratio to measure performance in server level and logical read to measure individual query level


Buffer cache hit ratio is a near-useless counter. By the time it drops significantly the server would have been having severe problems for a while.
http://www.simple-talk.com/sql/database-administration/great-sql-server-debates-buffer-cache-hit-ratio/

p.s. Over 3 year old thread.



Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1248830
Posted Sunday, January 27, 2013 10:40 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, September 14, 2015 11:16 PM
Points: 75, Visits: 67
Nice Explaination..

Thanks.
Post #1412139
Posted Monday, May 23, 2016 6:49 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, May 23, 2016 6:39 PM
Points: 1, Visits: 0
Really old thread now, but just to add a little bit to John's answer, logical reads should be the first thing to try to tune. It *might* not have a big impact on some queries on low traffic servers, compared to physical reads which are more costly, but as queries get more complex, and the load and concurrency starts to grow, logical reads start to result in more resources needed to process queries. That's because clearly the more data you need to process, the more time it will take, and if you start adding up many queries being executed at the same time, the load on the server can grow considerably. The data will also take more space, which should be less of a problem nowadays, with memory being so cheap.
Post #1789070
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse