Skip to content

Commit

Permalink
Merge pull request #384 from BrentOzarULTD/feature-382/brent
Browse files Browse the repository at this point in the history
#382 Adding dates/versions
  • Loading branch information
BrentOzar authored Jul 15, 2016
2 parents 2d598d2 + 1295e22 commit 0b43694
Show file tree
Hide file tree
Showing 4 changed files with 49 additions and 75 deletions.
45 changes: 12 additions & 33 deletions sp_Blitz.sql
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ ALTER PROCEDURE [dbo].[sp_Blitz]
AS
SET NOCOUNT ON;
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
SET @VersionDate = '20160626'
SET @VersionDate = '20160715'

IF @Help = 1 PRINT '
/*
Expand All @@ -53,6 +53,17 @@ AS
Unknown limitations of this version:
- None. (If we knew them, they would be known. Duh.)
Changes in v53.1 - 2016/07/15
- Warn about 2016 Query Store cleanup bug in Standard, Evaluation, Express:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/352
- Updating list of supported SQL Server versions:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/344
- Fixing bug in wait stats percentages:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/324
- For the full list of improvements and fixes in this version, see:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/milestone/3?closed=1
Changes in v53 - 2016/06/26
- BREAKING CHANGE: Standardized input & output parameters to be
consistent across the entire First Responder Kit. This also means the old
Expand All @@ -64,38 +75,6 @@ AS
when servers are in different data centers, different time zones. More info:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/288
Changes in v52 - 2016/06/02
- SQL Server 2016 compatibility. 2016 RTM ships with some questionable
database-level options like heaps in DWDiagnostics, target recovery
time changed in the DW* databases, and l_certSignSmDetach as a new
default sysadmin login, so ignoring those.
- If databases have an old compatibility level that does not support CTEs
then @CheckUserDatabaseObjects is set to 0 to avoid problems with
current checks. Get on the current compat level, Grandpa.
Changes in v51 - 2016/05/18
- Thomas Rushton added a check for dangerous third-party modules. (179)
More info: https://support.microsoft.com/en-us/kb/2033238
- New check for snapshot backups possibly freezing IO. Looking for 50GB+
backups that complete in under 60 seconds. (178)
- If there are 50+ user databases, you have to turn on @BringThePain = 1
in order to do @CheckUserDatabaseObjects = 1. (Speeds up sp_Blitz on
servers with hundreds or thousands of databases.)
- Reprioritized a bunch of checks, like moving security warnings down to
priority 230, so that you can use @IgnorePrioritiesAbove = 50 better.
- Bug fixes.
Changes in v50 - 2016/04/08
- Fixed bug in check ID 2 that would fail on a database with multiple log
files, that also has not had a backup in two weeks.
Changes in v49 - 2016/04/06
- Amazon RDS compatibility, but to do that, we have to skip a bunch of checks.
RDS does not allow you to query MSDB, configure TempDB, make
server-level sp_configure settings, etc.
For prior changes, see: http://www.BrentOzar.com/blitz/changelog/
Parameter explanations:
Expand Down
41 changes: 14 additions & 27 deletions sp_BlitzCache.sql
Original file line number Diff line number Diff line change
Expand Up @@ -186,6 +186,20 @@ Known limitations of this version:
Unknown limitations of this version:
- May or may not be vulnerable to the wick effect.
Changes in v3.1 - 2016/07/15:
- Show cost for stored procedures:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/339
- Warn about trace flags added at the query level, and global trace flags:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/361
- Add warnings about Remote Queries:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/315
- Do not show Forced Plans warning if the real cause is forced parameterization:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/343
- Fix divide-by-zero error if Cost Threshold for Parallelism is 0:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/358
- Fix warning for unparameterized query:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/334
Changes in v3.0 - 2016/06/26:
- BREAKING CHANGE: Standardized input & output parameters to be
consistent across the entire First Responder Kit. This also means the old
Expand Down Expand Up @@ -213,33 +227,6 @@ Changes in v3.0 - 2016/06/26:
Cleaned up documentation
Fixed bug related to CTFP being set to 0
Changes in v2.5.3 - 2016-04-28:
- Erik Darling added warnings for Expensive Sorts, Key Lookups, Remote Queries.
Will show up when they are >=50% of plan cost, and plan cost is >= 50% of
cost threshold for parallelism.
- Erik Darling found possible bug from 2014-04-30 trying to warn for tempdb
spills, which are not recorded in cached plans.
Changes in v2.5.2 - 2016-04-28:
- Erik Darling added warnings for Forced Serialization in 2012+ query plans.
Sorry, earlier versions.
- Erik Darling added Replication Distributor databases to list of system
databases to ignore.
Changes in v2.5.1 - 2016-03-15:
- Nick Molyneux fixed an overflow error, and did an amazing job of it.
Changes in v2.5.0 - 2015-10-23:
- Now with errors when required values are set to NULL. Thanks to Raul
Gonzalez for pointing this out.
- changing default @Top to 10
- Added a @skip_analysis to avoid the XML processing overhead
- Added QueryHash and QueryPlanHash to @ExportToExcel and expert mode
- Adding sort order for recent compiles.
- Fixing potential INT overflow in totals temp table
- Fixing slow sort performance on xpm and friends
- Added compilation info (memory, CPU, time) and plan size to output
- Re-structured XML processing for more better performance
MIT License
Expand Down
22 changes: 9 additions & 13 deletions sp_BlitzFirst.sql
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ AS
BEGIN
SET NOCOUNT ON;
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
SET @VersionDate = '20160626'
SET @VersionDate = '20160715'

IF @Help = 1 PRINT '
sp_BlitzFirst from http://FirstResponderKit.org
Expand All @@ -53,6 +53,14 @@ Known limitations of this version:
Unknown limitations of this version:
- None. Like Zombo.com, the only limit is yourself.
Changes in v25 - 2016/07/15
- Add new memory grants columns to 2012-2016 live queries output:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/362
- Add SQL login to live queries output:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/354
- Filter Perfmon counter display to skip counters with zeroes. Still logged to table though:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/356
Changes in v24 - 2016/06/26
- Renamed from sp_AskBrent.
- BREAKING CHANGE: Standardized input & output parameters to be
Expand All @@ -71,18 +79,6 @@ Changes in v24 - 2016/06/26
- Only show what queries are running now if @ExpertMode = 1. More info:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/266
Changes in v23 - April 27, 2016
- Christopher Whitcome fixed a bug in the new active-queries result set. Thanks!
Changes in v22 - April 19, 2016
- New @SinceStartup parameter. Defaults to 0. When turned on with 1, it sets
@Seconds = 0, @ExpertMode = 1, and skips results for what is running now and
the headline-news result set (the first two).
- If @Seconds = 0, output waits in hours instead of seconds. This only changes
the onscreen results - not the table results, because I try not to break the
existing table storage by changing output data.
- Added wait time per core per second (or per hour) in the ExpertMode wait
stats output.
MIT License
Expand Down
16 changes: 14 additions & 2 deletions sp_BlitzIndex.sql
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,8 @@ AS
SET NOCOUNT ON;
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
DECLARE @Version VARCHAR(30);
SET @Version = '4.0';
SET @VersionDate = '20160626';
SET @Version = '4.1';
SET @VersionDate = '20160715';
IF @Help = 1 PRINT '
/*
sp_BlitzIndex from http://FirstResponderKit.org
Expand Down Expand Up @@ -65,6 +65,18 @@ Known limitations of this version:
Unknown limitations of this version:
- We knew them once, but we forgot.
Changes in v4.1 - 2016/07/15:
- Compression information in @Mode = 2:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/18
- Use recently-modified check to improve indexes-not-in-use recommendations:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/220
- Alphabetical sort for @GetAllDatabases = 1, @Mode = 2 output:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/351
- Remove per-day cost filter for missing indexes in @Mode = 4:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/338
- Missing index benefit is now labeled per-day to make it more obvious:
https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/330
Changes in v4.0 - 2016/06/26:
- BREAKING CHANGE: Standardized input & output parameters to be
consistent across the entire First Responder Kit. This also means the old
Expand Down

0 comments on commit 0b43694

Please sign in to comment.