You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,11 +40,12 @@ To install, [download the latest release ZIP](https://github.com/BrentOzarULTD/S
40
40
41
41
The First Responder Kit runs on:
42
42
43
-
* SQL Server 2008, 2008R2, 2012, 2014, 2016, 2017, 2019 on Windows - yes, fully supported
44
-
* SQL Server 2017, 2019 on Linux - yes, fully supported except sp_AllNightLog and sp_DatabaseRestore, which require xp_cmdshell, which Microsoft doesn't provide on Linux
45
-
* SQL Server 2000, 2005 - not supported by Microsoft anymore, so we don't either
46
-
* Amazon RDS SQL Server - fully supported
47
-
* Azure SQL DB - It's a dice roll. Microsoft changes DMV contents in here without warning, so no guarantees.
43
+
* SQL Server 2012, 2014, 2016, 2017, 2019 on Windows - fully supported.
44
+
* SQL Server 2017, 2019 on Linux - yes, fully supported except sp_AllNightLog and sp_DatabaseRestore, which require xp_cmdshell, which Microsoft doesn't provide on Linux.
45
+
* SQL Server 2008, 200R2 - not officially supported since it's out of Microsoft support, but we try not to make changes that would break functionality here.
46
+
* SQL Server 2000, 2005 - not supported at all.
47
+
* Amazon RDS SQL Server - fully supported.
48
+
* Azure SQL DB - not supported. Some of the procedures work, but some don't, and Microsoft has a tendency to change DMVs in Azure without warning, so we don't put any effort into supporting it. If it works, great! If not, any changes to make it work would be on you. [See the contributing.md file](CONTRIBUTING.md) for how to do that.
48
49
49
50
50
51
## How to Get Support
@@ -207,6 +208,7 @@ You can log sp_BlitzFirst performance data to tables and then analyze the result
All of the above OutputTableName parameters are optional: if you don't want to collect all of the stats, you don't have to. Keep in mind that the sp_BlitzCache results will get large, fast, because each execution plan is megabytes in size.
212
214
@@ -297,7 +299,7 @@ Parameters you can use:
297
299
[*Back to top*](#header1)
298
300
299
301
300
-
## sp_BlitzQueryStore: Query Store Sale
302
+
## sp_BlitzQueryStore: How Has a Query Plan Changed Over Time
301
303
302
304
Analyzes data in Query Store schema (2016+ only) in many similar ways to what sp_BlitzCache does for the plan cache.
0 commit comments