#440 updating version dates and numbers

For the September release, closes #440.

Author: BrentOzar

sp_Blitz.sql

@@ -29,7 +29,7 @@ ALTER PROCEDURE [dbo].[sp_Blitz]
 AS
     SET NOCOUNT ON;
 	SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
-	SET @VersionDate = '20160715'
+	SET @VersionDate = '20160903'
 
 	IF @Help = 1 PRINT '
 	/*
@@ -55,27 +55,8 @@ 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
-         old output parameter @Version is no more, because we are switching to
-         semantic versioning. 	 
-	     https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/284
-	 - BREAKING CHANGE: The CheckDate field datatype is now DATETIMEOFFSET. This
-	   makes it easier to combine results from multiple servers into one table even
-	   when servers are in different data centers, different time zones. More info:
-	   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/288
+     Changes - for the full list of improvements and fixes in this version, see:
+     https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/milestone/4?closed=1
 
 
 	Parameter explanations:
@@ -3033,7 +3014,7 @@ AS
 						                        0 AS Priority ,
 						                        'Outdated sp_Blitz' AS FindingsGroup ,
 						                        'sp_Blitz is Over 6 Months Old' AS Finding ,
-						                        'http://www.BrentOzar.com/blitz/' AS URL ,
+						                        'http://FirstResponderKit.org/' AS URL ,
 						                        'Some things get better with age, like fine wine and your T-SQL. However, sp_Blitz is not one of those things - time to go download the current one.' AS Details
 	                        END
 
@@ -3160,7 +3141,7 @@ IF @ProductVersionMajor >= 10 AND @ProductVersionMinor >= 50
 							[sys].[dm_server_services]
 						  WHERE [status_desc] <> 'Running'
 						  AND [servicename] LIKE 'SQL Server Agent%'
-						  AND SERVERPROPERTY('Edition') NOT LIKE '%xpress%'
+						  AND CAST(SERVERPROPERTY('Edition') AS VARCHAR(1000)) NOT LIKE '%xpress%'
 
 					END; 
 				END;

sp_BlitzCache.sql

@@ -196,46 +196,9 @@ 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
-   old output parameter @Version is no more, because we are switching to
-   semantic versioning.
-   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/284
- - BREAKING CHANGE: The output table now adds a CheckDate field with a data
-   type of DATETIMEOFFSET, and removes SampleTime. More info:
-   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/288
- - Summary output now moved to the bottom instead of the top.
- - Erik Darling added columns to @ExpertMode = 1 results ~ONLY~
-     Will show up when you use an Output Table
-     Will not show up in Excel exports
-     -Query Hash More Info, and SQL Handle More Info  give you
-      sp_BlitzIndex style queries to get more information about specific queries
-     -Remove Plan Handle From Cache, and Remove SQL Handle From Cache give you
-      DBCC FREEPROCCACHE statements to remove items from Plan Cache
-	  -FIX: @IgnoreQueryHashes was not working. Should be working now.
- - Fixed ##bou_BlitzCacheResults not cleaned out after each pass. More info:
-   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/303
- - Fixed ##bou_BlitzCacheResults not filtered by session id. More info:
-   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/305
- - Erik Darling removed tempdb spills and expensive sorts from warnings.
-   Neither one works properly with cached plans.
-   Cleaned up documentation
-   Fixed bug related to CTFP being set to 0
+Changes - for the full list of improvements and fixes in this version, see:
+https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/milestone/4?closed=1
+
 
 
 MIT License

sp_BlitzFirst.sql

@@ -28,7 +28,7 @@ AS
 BEGIN
 SET NOCOUNT ON;
 SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
-SET @VersionDate = '20160715'
+SET @VersionDate = '20160903'
 
 IF @Help = 1 PRINT '
 sp_BlitzFirst from http://FirstResponderKit.org
@@ -53,31 +53,9 @@ 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
-   consistent across the entire First Responder Kit. This also means the old
-   old output parameter @Version is no more, because we are switching to
-   semantic versioning. More info:
-   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/284
- - BREAKING CHANGE: The CheckDate field datatype is now DATETIMEOFFSET. This
-   makes it easier to combine results from multiple servers into one table even
-   when servers are in different data centers, different time zones. More info:
-   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/288
- - Added BROKER_TRANSMITTER to list of ignorable wait types. More info:
-   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/268
- - Also ignore REDO_THREAD_PENDING_WORK, UCS_SESSION_REGISTRATION. More info:
-   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/174
- - Only show what queries are running now if @ExpertMode = 1. More info:
-   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/266
+Changes - for the full list of improvements and fixes in this version, see:
+https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/milestone/4?closed=1
+
 
 
 MIT License

sp_BlitzIndex.sql

@@ -34,8 +34,8 @@ AS
 SET NOCOUNT ON;
 SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
 DECLARE @Version VARCHAR(30);
-SET @Version = '4.1';
-SET @VersionDate = '20160715';
+SET @Version = '4.2';
+SET @VersionDate = '20160903';
 IF @Help = 1 PRINT '
 /*
 sp_BlitzIndex from http://FirstResponderKit.org
@@ -66,46 +66,9 @@ 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
-   old output parameter @Version is no more, because we are switching to
-   semantic versioning. 	 
-   https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/284
-- Bug fixes and improvements
-	- Erik Darling:
-		-Changed index_sanity_id to be NULLable in #IndexPartitionSanity
-		-Changed version check to only ever use LEFT JOIN query to get partition information.
-		 This was taking upwards of 6 minutes with 15k partitions.
-
-Changes in v3.0 - 2016/03/20:
- - Prioritized results
- - Moved URL to near the end of columns
- - Added 100k/day minimum benefit to high-value missing index recs
- - Expanded avg query cost on missing indexes to 4 decimal places
- - Formatted number of uses on missing indexes to use commas (money format)
- - Changed benefit formula to divide benefit number by uptime
- - When using either @Mode = 0 or @GetAllDatabases = 1, results are limited to:
-    *    Duplicate indexes where both are larger than @ThresholdMB
-    *    Blocking with a high threshold ( TBD)
-    *    Unread indexes larger than @ThresholdMB
-    *    Heaps larger than @ThresholdMB with updates or deletes
-    *    Identities about to run out of room
-    *    The top 20 missing indexes
-    *    Abnormal psychology stuff (as an FYI for query / index tuning)
- - Running @GetAllDatabases requires an override parameter (@BringThePain = 1) to run against 50+ databases
+Changes - for the full list of improvements and fixes in this version, see:
+https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/milestone/4?closed=1
+
 
 MIT License