Our free First Responder Kit is packed with scripts, worksheets, and checklists like:
It’s totally free because we’ve been there too. We’re database administrators and developers who know how hard it is to keep SQL Server fast and reliable, and we want to make your job easier. Later, if you need consulting for tough pains that have you stumped, we hope you’ll remember us and stop by.
First, thanks to 5 community volunteers for contributing code this month. In addition to lots of bug fixes, small stuff, and a new Github issue template (thanks, Konstantin Taranov) here’s the big improvements: sp_Blitz Changes @OutputServerName writes output to remote server (Haris Khan) – for years, these stored procs have had an @OutputServerName parameter just waiting to…
Exciting New Doodads When SP3 for 2012 dropped, we were all super excited by the new query tuning-centric features that were at our disposal. Now all we had to do was get people to install SP3! Great features like this make patching an easier sell. Now with SP2 for 2014 out, a lot of those…
So you’d like to fix a bug or contribute code to the First Responder Kit, but you’re new to Github. Let’s get started. 1. Open a new issue on Github. Go to the Github issues list for this repo, and start a new issue. Here’s the example that I’m going to work on today: In…
SQL Server 2012 SP3, 2014 SP2, and 2016 users are going to find a lot of stuff to love in here. The new per-query memory grants fields in the plan cache are exposed in sp_BlitzCache, and sp_BlitzFirst also shows memory grants for live running queries in @ExpertMode = 1. Here’s the details: sp_BlitzCache v3.1: Show…
If you’re using SQL Server 2016’s awesome new feature, Query Store, there’s a new bug with automatic cleanup. Books Online explains: Automatic data cleanup fails on editions other than Enterprise and Developer. Consequently, space used by the Query Store will grow over time until configured limit is reached, if data is not purged manually. If…
We’ve released the first fully open source version of our SQL Server First Responder Kit: sp_Blitz, sp_BlitzCache, sp_BlitzIndex, sp_BlitzRS, sp_BlitzTrace, and the newest member: the newly renamed sp_BlitzFirst. I wanted to rename sp_BlitzFirst because as an open source project, it’s going to have more than just my own answers as to why your SQL Server…
Yesterday we announced that we’re open sourcing our free SQL Server scripts, and one of those is sp_BlitzFirst. I originally named it that because it had a funny magic-8-ball type feature: if you pass in a question as a parameter, it gives you an answer like “Outlook not so good, Access even worse.” Cute, but now…
Lots of fun stuff out this week: sp_BlitzIndex® v3.0 adds prioritized, streamlined results. We see so many index design disasters, and we know you have a limited amount of time. Doug Lane put a ton of work into focusing the output on the most important issues, things that are easy-to-fix and will have an immediate performance improvement, and…
News broke recently of a dangerous data loss bug in SQL Server 2012 and 2014, and Aaron Bertrand explained which patch levels are affected. It’s kinda tricky, and I’m afraid most people aren’t even going to know about the bug – let alone whether or not they’re on a bad version. I added build number checking into…
Finding the worst queries in SQL Server is easy, right? You just query one of the dm_exec_* DMVs, bring in the SQL text and the execution plan, and then you spend hours looking at execution plans trying to figure out what’s wrong in the query, much less how to fix it. All that’s changing – we’re introducing sp_BlitzCache®….
