sys.dm_io_virtual_file_stats on SQL Server

Base on the attach result for IO query, how can it tell whether my server has I/O issue or not ? Tks

SELECT
cast(DB_Name(a.database_id) as varchar) as Database_name,
b.physical_name, *
FROM  
sys.dm_io_virtual_file_stats(null, null) a
INNER JOIN sys.master_files b ON a.database_id = b.database_id and a.file_id = b.file_id
ORDER BY Database_Name
SQL-IO-View.png
AXISHKAsked:
Who is Participating?
 
PadawanDBAConnect With a Mentor Operational DBACommented:
You're going to need to create a baseline and monitor the growth of the different pieces (the stall times as you have noted).  These are cumulative since the last server restart, so if you had a huge IO issue that caused all of those waits, you're still going to see them and they're going to skew your opinion.  Monitoring the growth of these stats on a periodic basis is going to give you a much better of: if you have an issue and when you have an issue.  With the knowledge of when you are having an issue (if you are), you are going to have a much better idea of what is going on from a sql process/storage processes perspective.  Another thing to keep in mind, is those stall stats are per spid, so if you have a process locking the file and there are 10 or so SPIDs that are waiting, you're going to have a 10x multiplier on the stall stats.

Edit:

Take a look at this article: http://blogs.msdn.com/b/kronos/archive/2010/04/13/introducing-sys-dm-io-virtual-file-stats.aspx?Redirected=true
0
 
AXISHKAuthor Commented:
Tks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.