June 27, 2013 at 12:08 am
Comments posted to this topic are about the item SQLServerCentral Runs sp_Blitz - Informational Items
June 27, 2013 at 7:27 am
Thanks for showing this to folks and including your findings!
A couple of quick notes - the Cost Threshold thing isn't really seconds. The BOL topic says it's seconds for a specific hardware config, but that means a long-dead machine at Microsoft. It's the query cost like you see in an execution plan - it's a combination of CPU and IO loads.
About the MSDB backup history - the problem with this (and I need to phrase it better on the findings page) is that if you use monitoring software that checks to make sure all databases have been backed up in the last X days, then that MSDB query ends up being one of the biggest resource hogs on the system. If you go through the plan cache and sort by total logical reads descending, the msdb backup check usually shows up in the top 10-20. MSDB just isn't indexed well to support most monitoring queries.
Thanks again, sir!
June 27, 2013 at 10:23 am
Thanks, Brent. I've made an update to the article, but the setting is probably OK for us right now.
I've also queried the SQL Monitor folks on the backup history. We haven't seen a query here cause issues with monitoring or the monitored systems, but we're checking.
July 6, 2013 at 8:24 am
I am wondering why you are using the older 1204 for deadlock information instead of (usually more useful) 1222.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
July 6, 2013 at 11:38 am
TheSQLGuru (7/6/2013)
I am wondering why you are using the older 1204 for deadlock information instead of (usually more useful) 1222.
No idea. I'll have to ask.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply