First off, I'm a SQL noob. My company uses an application called CCH ProFx Document, which uses a SQL backend. When it was first installed, it was running in VMWare Virtual Server. Approx. a month ago I converted the VMDK to Windows Server 2008 Hyper-V and the problems started happening. CCH claims its because I converted to Hyper-V. They think SQL is overwhelming the I/O path of Hyper-V. What can I do to find and correct any I/O problems I have? It's SQL 2005 Standard running on Windows Server Standard 2003, 4 GB of allocated RAM. The host is a Dell 2900 Dual Xeon Quad 2.5 Ghz w/ 8GB RAM. 3 15k 146GB SAS drives.