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: Documentation/sp_BlitzFirst_Checks_by_Priority.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@ Before adding a new check, make sure to add a Github issue for it first, and hav
6
6
7
7
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.
-[sp_BlitzBackups: How Much Data Could You Lose](#sp_blitzbackups-how-much-data-could-you-lose)
28
29
-[sp_AllNightLog: Back Up Faster to Lose Less Data](#sp_allnightlog-back-up-faster-to-lose-less-data)
@@ -43,7 +44,7 @@ The First Responder Kit runs on:
43
44
44
45
* SQL Server 2012, 2014, 2016, 2017, 2019 on Windows - fully supported.
45
46
* 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.
46
-
* 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.
47
+
* SQL Server 2008, 2008R2 - not officially supported since it's out of Microsoft support, but we try not to make changes that would break functionality here.
47
48
* SQL Server 2000, 2005 - not supported at all.
48
49
* Amazon RDS SQL Server - fully supported.
49
50
* 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.
@@ -364,6 +365,88 @@ It's designed for query tuners, so it includes things like memory grants, degree
Retrieves data from the output tables where you are storing your sp_BlitzFirst output.
371
+
372
+
Parameters include:
373
+
374
+
*@StartDate: When you want to start seeing data from , NULL will set @StartDate to 1 hour ago.
375
+
*@EndDate: When you want to see data up to, NULL will get an hour of data since @StartDate.
376
+
*@Databasename: Filter results by database name where possible, Default: NULL which shows all.
377
+
*@Servername: Filter results by server name, Default: @@SERVERNAME.
378
+
*@OutputDatabaseName: Specify the database name where where we can find your logged sp_BlitzFirst Output table data
379
+
*@OutputSchemaName: Schema which the sp_BlitzFirst Output tables belong to
380
+
*@OutputTableNameBlitzFirst: Table name where you are storing sp_BlitzFirst @OutputTableNameBlitzFirst output, we default to BlitzFirst - you can Set to NULL to skip lookups against this table
381
+
*@OutputTableNameFileStats: Table name where you are storing sp_BlitzFirst @OutputTableNameFileStats output, we default to BlitzFirst_FileStats - you can Set to NULL to skip lookups against this table.
382
+
*@OutputTableNamePerfmonStats: Table name where you are storing sp_BlitzFirst @OutputTableNamePerfmonStats output, we default to BlitzFirst_PerfmonStats - you can Set to NULL to skip lookups against this table.
383
+
*@OutputTableNameWaitStats: Table name where you are storing sp_BlitzFirst @OutputTableNameWaitStats output, we default to BlitzFirst_WaitStats - you can Set to NULL to skip lookups against this table.
384
+
*@OutputTableNameBlitzCache: Table name where you are storing sp_BlitzFirst @OutputTableNameBlitzCache output, we default to BlitzCache - you can Set to NULL to skip lookups against this table.
385
+
*@OutputTableNameBlitzWho: Table name where you are storing sp_BlitzFirst @OutputTableNameBlitzWho output, we default to BlitzWho - you can Set to NULL to skip lookups against this table.
386
+
*@MaxBlitzFirstPriority: Max priority to include in the results from your BlitzFirst table, Default: 249.
387
+
*@BlitzCacheSortorder: Controls the results returned from your BlitzCache table, you will get a TOP 5 per sort order per CheckDate, Default: 'cpu' Accepted values 'all' 'cpu' 'reads' 'writes' 'duration' 'executions' 'memory grant' 'spills'.
388
+
*@WaitStatsTop: Controls the Top X waits per CheckDate from your wait stats table, Default: 10.
389
+
*@ReadLatencyThreshold: Sets the threshold in ms to compare against io_stall_read_average_ms in your filestats table, Default: 100.
390
+
*@WriteLatencyThreshold: Sets the threshold in ms to compare against io_stall_write_average_ms in your filestats table, Default: 100.
391
+
*@BringThePain: If you are getting more than 4 hours of data from your BlitzCache table with @BlitzCacheSortorder set to 'all' you will need to set BringThePain to 1.
392
+
*@Maxdop: Control the degree of parallelism that the queries within this proc can use if they want to, Default = 1.
393
+
*@Debug: Show sp_BlitzAnalysis SQL commands in the messages tab as they execute.
394
+
395
+
Example calls:
396
+
397
+
Get information for the last hour from all sp_BlitzFirst output tables
Exclude specific tables e.g lets exclude PerfmonStats by setting to NULL, no lookup will occur against the table and a skipped message will appear in the resultset
We are likely to be hitting some big tables here and some of these queries will require scans of the clustered indexes as there are no nonclustered indexes to cover the queries by default, keep this in mind if you are planning on running this in a production environment!
429
+
430
+
I have noticed that the Perfmon query can ask for a big memory grant so be mindful when including this table with large volumes of data:
431
+
432
+
```SQL
433
+
SELECT
434
+
[ServerName]
435
+
,[CheckDate]
436
+
,[counter_name]
437
+
,[object_name]
438
+
,[instance_name]
439
+
,[cntr_value]
440
+
FROM [dbo].[BlitzFirst_PerfmonStats_Actuals]
441
+
WHERE CheckDate BETWEEN @FromDate AND @ToDate
442
+
ORDER BY
443
+
[CheckDate] ASC,
444
+
[counter_name] ASC
445
+
```
446
+
447
+
[*Back to top*](#header1)
448
+
449
+
367
450
## sp_BlitzBackups: How Much Data Could You Lose
368
451
369
452
Checks your backups and reports estimated RPO and RTO based on historical data in msdb, or a centralized location for [msdb].dbo.backupset.
0 commit comments