We have an ETL process that kicks off at 4am every Sunday Morning. This process used to take 2 - 2 1/2 hours to run, not it is taking 5-6 hours. This issue seemed to start after upgrading the VM from Virtual Server 2005 R2 to Hyper-V. Months ago we were trying to fix the SAN performance issues by upgrading the VM, but that didn't fix the problem. The Hyper-V VM is running 4 procs, 6 gig ram and using high speed LUN's. The ETL job is kicked off as a MS scheduled job. The VM is running Server 2003 Standard R2 Standard SP2 w/ SQL server 2005 sp2. When monitoring the process as it is running, the CPU usage and RAM usage is minimal to moderate, never even close to utilizing the full CPU or RAM usage. There is a massive amount of I/O taking place, which is typical in an ETL process. So the problem seems to be through-put, however, we cannot find a solution. We are using high-speed luns on the SAN. We also added the /3gb switch to the startup. Actual CPU utilization is hovering from 30 to 65%, ram usage is minimal. TempDB is getting hammered and disk load is maxxed out. The I/O wait states are very high.