Blog

Today, we’ve got a big one, and it’s all thanks to you.

For the last couple of versions, I haven’t added any big features because I’d been focused on the plan cache improvements. Today, though, we’ve got a big one with all kinds of health-checking improvements – and they’re all thanks to your contributions.

  • Lori Edwards @LoriEdwards http://sqlservertimes2.com – Did all the coding in this version! She did a killer job of integrating improvements and suggestions from all kinds of people.
  • Chris Fradenburg @ChrisFradenburg http://www.fradensql.com – added a check to identify globally enabled traceflags
  • Jeremy Lowell @DataRealized http://datarealized.com added a check for non-aligned indexes on partitioned tables
  • Paul Anderton @Panders69 added a check for high VLF count
  • Ron van Moorsel tweaked and added a couple of checks including whether tempdb was set to autogrow, and checking for linked servers configured with the SA login
  • Shaun Stuart @shaunjstu http://shaunjstuart.com added several changes – the much-desired check for the last successful DBCC CHECKDB, checking ot make sure that @@SERVERNAME is not null, and updated check 1 to make sure the backup was done on the current server
  • Sabu Varghese fixed a typo in check 51
  • We added a check to determine if a failsafe operator has been configured
  • Added a check for transaction log files larger than data files suggested by Chris Adkins
  • Fixed a bunch of bugs for oddball database names (like apostrophes).

Here’s how to use it:

Head on over to BrentOzar.com/blitz and let us know what you think. Enjoy!

↑ Back to top
  1. Thanks as always, looking forward to testing. Ran into an issue last week where I needed to get the DBCC info, wrote my own script, and was looking for was to integrate it with sp_blitz. Beat me to it.

  2. VLF appears to only be checking for where it is a snapshot?

    WHERE EXISTS (SELECT name FROM master.sys.databases
    WHERE source_database_id is not null)

    • Hi Todd – thanks for checking the details! Another user caught that and we’ve uploaded new code. The current version is v15. Updates came fast & furious this morning!

  3. ‘Last good DBCC CHECKDB over 2 weeks old’ is not working here on MSSQL 2008 R2.

    https://gist.github.com/4257321

    Also, is there a reason for missing NO_INFOMSGS on DBCC DBINFO?

    • WQW – ooo, nice code contribution! I love that, nice work. I’m adding that to v15 and crediting you. I’m aiming to have it out this week – got a whole bunch of code contributions.

  4. Hi Brent

    Thanks for the great content and interesting articles.

    I removed the below from facebook. Thought would be better to add it here.

    When I clicked on the short link you provided on facebook, I am getting this message:
    The link you are trying to visit has been reported as abusive by Facebook users. To learn more about staying safe on the internet, visit Facebook’s Security Page. Please also read the Wikipedia articles on malware and phishing.

    Not sure if it’s just my connection. but thought to let you know, maybe you can double check.

    Regards,
    Alin

  5. Thanks for this great stuff! Very helpful!

  6. Awesome work, I am using this on my 90 servers to clean up some oddities that have been found.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

css.php