| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 8 months |
| seen | Jan 4 at 20:30 | |
| stats | profile views | 1 |
|
Sep 23 |
awarded | Student |
|
Sep 21 |
awarded | Scholar |
|
Sep 21 |
comment |
Production SQL Server High CPU for a Single Query Yup. That's exactly what was happening, Aaron. |
|
Sep 21 |
accepted | Production SQL Server High CPU for a Single Query |
|
Sep 21 |
comment |
Production SQL Server High CPU for a Single Query I just got it fixed. I cleared the cache for that query and it is now performing optimally again. Thanks for all the suggestions above. This was very helpful in getting to the root of the problem. |
|
Sep 21 |
comment |
Production SQL Server High CPU for a Single Query Auto Update Statistics is ON. tempdb is pretty much in its default settings. I have viewed the waits and don't see anything holding the query up. What were you thinking I should look for specifically in the plan cache? I see the query in the cache and it is about 3MB in size. |
|
Sep 21 |
asked | Production SQL Server High CPU for a Single Query |