Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 IO analysis

Author  Topic 

coolerbob
Aged Yak Warrior

841 Posts

Posted - 2008-03-13 : 05:22:29
I'm looking to see if I have a issue with excessive IO activity caused by less-than-ideal access patterns.

So I've run this query to look at logical and physical reads for logical writes:

select sql_handle, plan_handle,
total_physical_reads, last_physical_reads,
min_physical_reads, max_physical_reads,
total_logical_writes, last_logical_writes,
min_logical_writes, max_logical_writes,
total_logical_reads, last_logical_reads,
min_logical_reads, max_logical_reads
from sys.dm_exec_query_stats

The question is, when can it be considered excessive?
Or can you just order the results by descending order and see if you can make improvements on the worst ones?

The same goes for this query for pageiolatch wait counters and times for indexes:
select database_id, object_id, index_id, partition_number, page_io_latch_wait_count, page_io_latch_wait_in_ms
from sys.dm_db_index_operational_stats (null,null,null,null)

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-03-13 : 23:05:45
You need check execution plan as well. Make some changes on index if necessary then compare disk i/o.
Go to Top of Page

jackv
Master Smack Fu Yak Hacker

2179 Posts

Posted - 2008-03-14 : 02:45:34
Have you considered looking at wait stats. They can give you very good clues as to underlying problems. DBCC SQLPERF(WAITSTATS)

Jack Vamvas
--------------------
Search IT jobs from multiple sources- http://www.ITjobfeed.com
Go to Top of Page
   

- Advertisement -