﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 7,2000 / Performance Tuning  / SQL Profiler Reads vs Set Statistics IO logical reads / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sun, 19 May 2013 11:01:46 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: SQL Profiler Reads vs Set Statistics IO logical reads</title><link>http://www.sqlservercentral.com/Forums/Topic1394734-65-1.aspx</link><description>more information:  I found out that on the server with greater reads, it always generates a CacheInsert event, but on the server with lesser reads, it generates a CacheHit event.  Maybe that's the cause of the extra reads.  Further, the procedure cache hit ration is very low (20%) and the cache size is small (only a few MB).  so now my question is - why is the query plan not being written to cache (or aged out immediately).</description><pubDate>Mon, 10 Dec 2012 12:15:37 GMT</pubDate><dc:creator>Steve-443559</dc:creator></item><item><title>SQL Profiler Reads vs Set Statistics IO logical reads</title><link>http://www.sqlservercentral.com/Forums/Topic1394734-65-1.aspx</link><description>I created a table with a single varchar(10) column and ran a select statement against it.  In Profiler, it shows 25 reads but in SSMS using Statistics IO, it shows only 1 logical read.  What is the difference between the two values?  Also, I did the same thing against another SQL 2005 server and the reads in Profiler show only 3 and I'm trying to figure out why one shows 3 and one shows 25 for such a simple statement.  The table has no triggers, indexes.Thanks.</description><pubDate>Mon, 10 Dec 2012 11:56:28 GMT</pubDate><dc:creator>Steve-443559</dc:creator></item></channel></rss>