Why do updates inside of a SQL transaction still need disk IO?
Posted
by usr
on Stack Overflow
See other posts from Stack Overflow
or by usr
Published on 2010-04-07T19:32:48Z
Indexed on
2010/04/07
21:13 UTC
Read the original article
Hit count: 239
In SQL Profiler you can see that very simple updates to a table by primary key take about 10-30ms each. On about every 10th update the write column shows 1, on all other updates it shows 0. This must mean that about every 10th update statement still requires disk IO. I wonder why that is. Would it not be more efficient queue up all IO until the transaction commits?
© Stack Overflow or respective owner
