sp_Blitz® Version 18 Out: Lots of Bug Fixes

There’s a new version in town.  v18 adds new checks looking for:

  • Backups stored on the same drive letters as user databases (Thanks @AlinSelicean!)
  • Agent jobs that don’t have failure notifications set up (Thanks @Thirster42!)
  • Shows free drive space per drive letter if you pass @CheckServerInfo = 1 in. We don’t consider this a problem – we just show additional info if you use this parameter.
  • Added the elevated database permissions check back in (whoops! dropped it accidentally)

Plus bug fixes and improvements including:

  • Lots and lots of typos
  • Ignore max file sizes for filestream data files
  • Switched a lot of @@SERVERNAME usage out with SERVERPROPERTY(‘ServerName’) because in some SQL Server cloud implementations, those don’t match, and it’s okay.
  • Changed database name variables to be NVARCHAR(128) to handle those monster SharePoint databases
  • Improved the non-aligned-indexes check to return results even if the index hasn’t been used

And more.  Version 17 also added a neat new exclusions table parameter – if you’re the kind of DBA who wants to automate sp_Blitz® data collection throughout the environment, but you want to skip certain checks or certain databases, you can do that now.  I haven’t written up full instructions on that, but the basic idea is pretty obvious within reading the first 100-200 lines of the code.

As always, you can get the latest version and instructions from http://www.BrentOzar.com/blitz/.  If you’d like to contribute code, you can email us at Help@BrentOzar.com.  I’m still working through a backlog of about 20 more new check contributions, and we’ve got some fun stuff coming – including a thank-you page listing the contributors and their work.

Previous Post
DBAs vs Devs: ORMs, Caching & Access to Prod
Next Post
3 Things You Need to Stop Doing to Your Database Server

14 Comments. Leave new

  • Wes Crockett
    April 5, 2013 9:47 am

    Awesome! I was just researching the possibility of restricting the databases it runs against as I have a DB server with about 30 production DB’s on it and it takes FOREVER to run and I want to use it to triage individual DB issues.

    That said, there is a discrepancy in your article: mentions v18 being released but then mentions v17 for the new features. Also, going to the download page, v17 is still what comes up.

    Thank you,
    Wes

    Reply
    • Hmm – may need to refresh your browser, perhaps. Just tested here and it shows v18. If that doesn’t work, can you give me the address in your browser where you’re seeing v17? Thanks!

      Reply
    • Also, just to be clear – in the post, I also mention new features that v17 brought. That’s on purpose – I’m bringing readers up to speed. 😀

      Reply
      • Wes Crockett
        April 5, 2013 10:33 am

        AAAH! ok… it did end up refreshing to v18 after a few mins.

        Thanks for all you and your team does!

        Reply
  • Great work as always. Question that I could probably answer myself but this might be quicker. Do the CheckID’s stay the same across versions for existing checks? I’m working on some automation and have that based on CheckID.

    Reply
    • Thanks sir! Yes, we try not to change check IDs for that exact reason. I’ve had to change a couple recently because I was sloppy and had two checks with the same ID, but hopefully there’s no more of those left. Would it be useful for me to publish a list of checks by ID?

      Reply
  • sebastien Piche
    April 5, 2013 12:20 pm

    nice to have if have mount drive into c: maybe use drive name not juste drive leter fro checkid 26

    Reply
  • A new sp_Blitz is out?! Well, yes, I would like to partake in this delicious delectable delight! Thank you! 🙂

    Reply
  • “the basic idea is pretty obvious within reading the first 100-200 lines of the code.” Hahaha, I need to start using that line again.

    Reply
  • Giddyup!

    Reply
  • ” – Improved check 78 for implicit conversion so that it checks sys.sql_modules for the is_recompiled bit flag rather than scanning the source code.”

    I think this v17 change was reverted in v18. The v18 code still scans for the “WITH RECOMPILE” text.

    Reply
  • Rudy Panigas
    April 22, 2013 8:50 am

    Hello Sir! Great script. I do have a question about the versions. You mentioned version 18 but when I open the script it said “sp_Blitz (TM) v20 – April 12, 2013”. Can I assume that the version you have for download is a newer version? Either way, it’s awesome!!

    Thanks,

    Rudy

    Reply

Leave a Reply

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

Fill out this field
Fill out this field
Please enter a valid email address.

Menu
{"cart_token":"","hash":"","cart_data":""}