November 1, 2006 at 12:36 pm
Profiler is not reporting what I was expecting in the "writes" column. I have a server with lots of right activity and lots of updates/inserts showing up in profiler, but the "writes" column is 0 99.7% of the time. The reads associated with the updates/inserts are registering under "reads" (checking PK's etc.) but writes are not.
So, I started to wonder if "writes" are showing up as zero because a page may be written to many times before it is flushed to disk. If that is the case, I started to wonder what actually generates a "write" greater than zero.
Perhaps procs that directly or indirectly create work tables are the only statements generating writes within profiler??? Anyone know?
November 2, 2006 at 5:58 am
reads and writes are page ops which isn't always the same as table row/column updates.
If you create a table just over 4k wide, each insert should generate a page write.
If you have a 6k char column and update it you should get a page write for each update
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply