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.
| Author |
Topic |
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
 Posted - 2011-02-11 : 12:16:25
|
| I have a regular ETL query that will, on occassion, take hours to complete; usual time is about a minute. Today, while investigating an active case of this happening, I came across this information from the sys.dm_exec_requests call and it does not add up for me:Status = RunningCommand = InsertBlocking_session_id = 0 (Sounds good to me!)wait_type = Null (Still sounds good!!)open_transaction_count = 2cpu_time = 16783594 (Crazy!!!)The I/O activity is essentially zero. I checked this via SQL and confirmed it at the SAN level, too.The daily load is not larger or smaller than any other day to any significant degree. The actual INSERT is the load of the cleansed ETL data into the main production data table.I'm open to any and all suggestions.Many thanks.=======================================Elitism is the slur directed at merit by mediocrity. -Sydney J. Harris, journalist (1917-1986) |
|
|
|
|
|
sys.dm_exec_requests - Hung Query