2019_02 Release (#1977)

* Updating readme.md for sp_DatabaseRestore

Documenting @ExistingDBAction for https://dba.stackexchange.com/questions/226145/sp-databaserestore-msg-50000.

* 1900 sp_BlitzIndex add histograms

When @TableName is specified and sys.dm_db_stats_histogram is available. Closes #1900.

* #1903 sp_Blitz SQLServerCheckup

Adding filter for that app name. Closes #1903.

* #1905 sp_BlitzIndex remove BOU link

Nothing against BOU, just don't need it in that particular place. Closes #1905.

* #1908 Update copyright dates

Ah, the glamour. Closes #1908.

* Issue #1904 Change RAISERROR 'severity' for that should trigger throw and error.

* Issue #1910 Add SQL Server version check before choosing 'memory grant' as the @BlitzCacheSortOrder.

* Issue #1910 Add temp table creation.

* #1914 sp_BlitzIndex partition error severity

Dropping severity level from 16 to 0 since we're logging it in the result set anyway. Closes #1914.

* Issue 1894 Moved RESTORE HEADERONLY up

* LF line endings

* added some extra checks + corrected some nesting

* rebase and line endings

* Web site commit

Does this fix line endings?

* #1916 sp_Blitz ignore backup on TempDB drive

Closes #1916.

* Auto line endings

Dealing with sp_DatabaseRestore's line endings.

* 1919 sp_Blitz ignoring a few checks for Managed Instances (#1920)

* 1919 sp_Blitz ignoring a few checks for Managed Instances

Working on #1919.

* #1919 sp_Blitz excluding restored databases

When checking backup history. Working on #1919.

* #1919 sp_Blitz ignore some checks on Mgd Instances

Changing RCSI wording on Azure SQL DB. Working on #1919.

* #1921 Sp_BlitzIndex Add Drop and Create Columns to Output (#1923)

Joined output query to #IndexCreateTsql to retrieve the CreateTsql already generated earlier in the script.  Created Drop TSQL based off evaluating what type of index was present.

* #1921 sp_BlitzIndex adding drops (#1924)

Moving drop and create TSQL to the end of mode 2's results. Closes #1921.

* #1925 sp_Blitz AWS RDS detection (#1926)

Don't just rely on EC2 VM name to detect RDS. Also adds a new result noting that checks were skipped. Closes #1925.

* #1927 sp_BlitzIndex skip rdsadmin db (#1928)

GetAllDatabases = 1 fails when it hits rdsadmin because they're referring to the resource db. Closes #1927.

* 2019_01 Release (#1931)

Prep work for the release - changing version numbers, building build scripts.

* #1933 sp_BlitzIndez Azure SQL DB (#1934)

Check for DaysUptime is null. Closes #1933.

* 1936 Deprecate Power BI Dashboard (#1937)

Closes #1936.

* sp_BlitzFirst - Decimals - Fixes #1940 (#1941)

* batch requests & waits/core/sec are now decimals

* also updated final data set for consistency

* 1950 sp blitz lock azure sql db hyperscale (#1951)

* #1950 sp_BlitzLock Azure SQL DB Hyperscale

Fixes #1950.

* #1950 sp_BlitzLock Azure SQL DB Hyperscale

Oops, forgot my semicolon. Fixes #1950.

* #1947 sp_BlitzIndex stats for current db (#1955)

Can only get stats if you're in the database you're analyzing. Closes #1947.

* #1952 sp_BlitzIndex Fix INSERT query column order (#1954)

* remove table name from create index script (#1942)

* Add Version Checking  for all SP (#1949)

* Update sp_BlitzCache.sql

DECLARE @BlitzCacheVersion     VARCHAR(30);
DECLARE @BlitzCacheVersionDate DATETIME2;
EXEC dbo.sp_BlitzCache @VersionCheckMode = 1, @Version = @BlitzCacheVersion OUTPUT, @VersionDate = @BlitzCacheVersionDate OUTPUT ;
SELECT @BlitzCacheVersion as BlitzCacheVersion , @BlitzCacheVersionDate as BlitzCacheVersionDate

* Update sp_BlitzFirst.sql

* Update sp_BlitzIndex.sql

* Update sp_BlitzLock.sql

* Update sp_BlitzQueryStore.sql

* Update sp_BlitzWho.sql

* Update sp_DatabaseRestore.sql

* Update sp_BlitzInMemoryOLTP.sql

* Update sp_foreachdb.sql

* Update sp_ineachdb.sql

* Update sp_BlitzBackups.sql

* Update sp_Blitz.sql

* Update sp_AllNightLog_Setup.sql

* Update sp_AllNightLog.sql

* Update sp_BlitzInMemoryOLTP.sql

* Update sp_BlitzLock.sql

* sp_ineachdb version check

Tweaking #1948 so it works. Closes #1948.

* Update sp_BlitzCache.sql (#1953)

Complete the join between #missing_index_detail and ##bou_BlitzCacheProcs as otherwise on servers running jobs with many steps, each missing indices will cause #missing_index_pretty to grow exponentially, causing sp_BlitzCache to run for hours.

* Fixes #1943 - sp_Blitz check if SSIS/SSRS/SSAS are running (#1957)

* Update sp_Blitz.sql

* Update sp_Blitz.sql

* Update sp_Blitz Checks by Priority.md

* Update sp_Blitz Checks by Priority.md

* Update sp_Blitz Checks by Priority.md

* altered search strings

because *of course* there's white space. shouldn't hurt too badly because there aren't many services running on sql boxes (hopefully)

* #1943 adding URL (#1960)

For new SSAS/IS/RS check. Closes #1943.

* sp_BlitzCache additional plural checks for @sortorder (#1963)

* additional plural checks

added in plural checks, also raised error to 16 when invalid sort order is chosen.

* removed unnecessary checks

* minor typo (#1965)

* #1967 sp_Blitz updating supported versions (#1969)

SQL 2012 pre-SP4 is out of support. Closes #1967.

* #1935 sp_BlitzCache Azure compatibility (#1972)

Azure SQL DB compatibility and removing bou from global temp table names. Closes #1935.

* #1973 sp_BlitzIndex truncation error (#1974)

Fixes #1973.

* #1971 add POOL_LOG_RATE_GOVERNOR as poison (#1975)

Closes #1971.

* #1966 fix sp_Blitz check IDs (#1976)

203 and 224 were swapped in the documentation. Closes #1966.

* 20190219 bumping version numbers

To prep for imminent release...

* 20190219 release

Updating install-all-scripts with new versions.

Author: BrentOzar

CONTRIBUTING.md

@@ -53,16 +53,6 @@ Your code must handle:
 We know that's a pain, but that's the kind of thing we find out in the wild. Of course you would never build a server like that, but...
 
 
-### Contributing Changes to Power BI
-
-Power BI files are binary files that don't work well with Git source control. Rather than sending someone your changed Power BI files, here's what you need to do:
-
-1. Make the changes on your side, test them, and make sure they work.
-2. In the Github issue you created above (in the How to Build Features section), add step-by-step instructions for someone else to make the same change to the master Power BI files.
-3. The First Responder Kit maintainers will review your changes and try to reproduce your results with the same steps. If they produce the right results, congratulations! They'll be saved permanently.
-
-Why not just email your file to the maintainers? Well, lots of folks may be working on slightly different changes at the same time, and we need to be able to fold everyone's changes together at different points in time.
-
 ### Contributing T-SQL Code: Git Flow for Pull Requests
 <a name="git-flow"></a>
 

…stResponderKit Example for Training.pbix …stResponderKit Example for Training.pbixPower BI/FirstResponderKit Example for Training.pbix renamed to Deprecated/Power BI/FirstResponderKit Example for Training.pbix Power BI/FirstResponderKit Example for Training.pbix renamed to Deprecated/Power BI/FirstResponderKit Example for Training.pbix

@@ -1,5 +1,5 @@
 #Set your file path
-$FilePath = "C:\Users\edarl\OneDrive\Documents\GitHub\SQL-Server-First-Responder-Kit"
+$FilePath = "C:\temp\SQL-Server-First-Responder-Kit"
 
 
 #All Core Blitz Without sp_BlitzQueryStore

Power BI/FirstResponderKit.pbit …precated/Power BI/FirstResponderKit.pbitPower BI/FirstResponderKit.pbit renamed to Deprecated/Power BI/FirstResponderKit.pbit Power BI/FirstResponderKit.pbit renamed to Deprecated/Power BI/FirstResponderKit.pbit

@@ -6,14 +6,14 @@ Before adding a new check, make sure to add a Github issue for it first, and hav
 
 If you want to change anything about a check - the priority, finding, URL, or ID - open a Github issue first. The relevant scripts have to be updated too.
 
-CURRENT HIGH CHECKID: 223.  
-If you want to add a new one, start at 224.
+CURRENT HIGH CHECKID: 224.  
+If you want to add a new one, start at 225.
 
 | Priority | FindingsGroup | Finding | URL | CheckID |
 |----------|-----------------------------|---------------------------------------------------------|------------------------------------------------------------------------|----------|
 | 0 | Outdated sp_Blitz | sp_Blitz is Over 6 Months Old | https://www.BrentOzar.com/blitz/ | 155 |
-| 0 | Informational | @CheckUserDatabaseObjects Disabled | https://www.BrentOzar.com/blitz/ | 223 |
-| 0 | Informational | Some Checks Skipped | https://www.BrentOzar.com/blitz/ | 204 |
+| 0 | Informational | @CheckUserDatabaseObjects Disabled | https://www.BrentOzar.com/blitz/ | 204 |
+| 0 | Informational | Some Checks Skipped | https://www.BrentOzar.com/blitz/ | 223 |
 | 1 | Backup | Backing Up to Same Drive Where Databases Reside | https://www.BrentOzar.com/go/backup | 93 |
 | 1 | Backup | Backups Not Performed Recently | https://www.BrentOzar.com/go/nobak | 1 |
 | 1 | Backup | Encryption Certificate Not Backed Up Recently | https://www.BrentOzar.com/go/tde | 202 |
@@ -240,6 +240,7 @@ If you want to add a new one, start at 224.
 | 200 | Performance | Query Store Disabled | https://www.BrentOzar.com/go/querystore | 163 |
 | 200 | Performance | Snapshot Backups Occurring | https://www.BrentOzar.com/go/snaps | 178 |
 | 200 | Performance | User-Created Statistics In Place | https://www.BrentOzar.com/go/userstats | 122 |
+| 200 | Performance | SSAS/SSIS/SSRS Installed | https://www.BrentOzar.com/go/services | 224 |
 | 200 | Reliability | Extended Stored Procedures in Master | https://www.BrentOzar.com/go/clr | 105 |
 | 200 | Surface Area | Endpoints Configured | https://www.BrentOzar.com/go/endpoints/ | 9 |
 | 210 | Non-Default Database Config | ANSI NULL Default Enabled | https://www.BrentOzar.com/go/dbdefaults | 135 |