September 17, 2009 at 7:23 am
I'm looking to find out what is the meaning of the "Read" column in a profiler trace.
So far I've found this:
Number of logical disk reads performed by the event. Only reported for events that perform data reads.
Does it mean the number of requested read I/O only (and we don't know how many pages were read) or is it the number of disk read for loading an entire page in memory (therefore the memory load would be (# of reads * 8k)) ?
September 17, 2009 at 9:29 am
My understanding is that SQL Server only reads and writes in 8KB pages so the number of reads would be the number of 8KB pages read into memory for the operation.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 17, 2009 at 9:40 am
Hello Jack,
This is also my understanding when SQL need to read (a page at the time) but I need to make sure what this profiler number mean.
having x read i/o is different for me than having x page read and I want to clarify this
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply