Skip to content

Release: sp_PerfCheck v2.3 + README accuracy fixes #677

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
erikdarlingdata merged 1 commit into from
Feb 18, 2026
Merged

Release: sp_PerfCheck v2.3 + README accuracy fixes #677

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 27 additions & 15 deletions README.md
View file
Open in desktop

Large diffs are not rendered by default.

4 changes: 3 additions & 1 deletion sp_HealthParser/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,12 @@ Typical result set will show you:
| @end_date | datetimeoffset | latest date to show data for, will be internally converted to UTC | a reasonable date | current date |
| @warnings_only | bit | only show rows where a warning was reported | NULL, 0, 1 | 0 |
| @database_name | sysname | database name to show blocking events for | the name of a database | NULL |
| @wait_duration_ms | bigint | minimum wait duration | the minimum duration of a wait for queries with interesting waits | 0 |
| @wait_duration_ms | bigint | minimum wait duration | the minimum duration of a wait for queries with interesting waits | 500 |
| @wait_round_interval_minutes | bigint | interval to round minutes to for wait stats | interval to round minutes to for top wait stats by count and duration | 60 |
| @skip_locks | bit | skip the blocking and deadlocking section | 0 or 1 | 0 |
| @skip_waits | bit | skip the wait stats section | 0 or 1 | 0 |
| @pending_task_threshold | integer | minimum number of pending tasks to display | a valid integer | 10 |
| @use_ring_buffer | bit | use ring_buffer target instead of file target for faster collection | 0 or 1 | 0 |
| @log_to_table | bit | enable logging to permanent tables | 0 or 1 | 0 |
| @log_database_name | sysname | database to store logging tables | valid database name | NULL |
| @log_schema_name | sysname | schema to store logging tables | valid schema name | NULL |
Expand Down
5 changes: 3 additions & 2 deletions sp_HumanEvents/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,8 @@ Misuse of this procedure can harm performance. Be very careful about introducing
| @object_schema | sysname | (inclusive) the schema of the object you want to filter to; only needed with blocking events | a stringy thing | dbo |
| @requested_memory_mb | integer | (>=) the memory grant a query must ask for to have data collected | an integer | 0 |
| @seconds_sample | tinyint | the duration in seconds to run the event session for | an integer | 10 |
| @gimme_danger | bit | used to override default minimums for query, wait, and blocking durations. | 1 or 0 | 0 |
| @gimme_danger | bit | used to override default duration minimums for wait events, including zero-duration waits | 1 or 0 | 0 |
| @target_output | sysname | output target for extended events | "ring_buffer" or "event_file" (event_file not available for Azure SQL DB or Managed Instance) | "ring_buffer" |
| @keep_alive | bit | creates a permanent session, either to watch live or log to a table from | 1 or 0 | 0 |
| @custom_name | sysname | if you want to custom name a permanent session | a stringy thing | intentionally left blank |
| @output_database_name | sysname | the database you want to log data to | a valid database name | intentionally left blank |
Expand Down Expand Up @@ -192,7 +193,7 @@ ON SERVER
| @log_schema_name | sysname | schema to store logging tables | a valid schema name | NULL |
| @log_table_name_prefix| sysname | prefix for all logging tables | a valid table name prefix | 'HumanEventsBlockViewer' |
| @log_retention_days | integer | Number of days to keep logs, 0 = keep indefinitely | a valid integer | 30 |
| @max_blocking_events | bigint | maximum blocking events to analyze, 0 = unlimited | 0 to 9223372036854775807 | 5000 |
| @max_blocking_events | integer | maximum blocking events to analyze, 0 = unlimited | 0 to 2147483647 | 5000 |
| @help | bit | how you got here | 0 or 1 | 0 |
| @debug | bit | dumps raw temp table contents | 0 or 1 | 0 |
| @version | varchar | OUTPUT; for support | none; OUTPUT | none; OUTPUT |
Expand Down
2 changes: 1 addition & 1 deletion sp_IndexCleanup/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,5 +98,5 @@ EXECUTE dbo.sp_IndexCleanup
- When using @get_all_databases, results for all databases are combined in a single result set
- The index_count column for the SUMMARY row in the output table will likely indicate a lower number than is shown at the DATABASE level. The SUMMARY level only includes indexes that have been analyzed; excluding things like clustered indexes, heaps, xml indexes, etc. The DATABASE level index_count value is the total number of indexes in the database.

Copyright 2024 Darling Data, LLC
Copyright 2026 Darling Data, LLC
Released under MIT license
2 changes: 1 addition & 1 deletion sp_LogHunter/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ It helps you give you a fuller, better picture of any bad stuff happening.
| @days_back | integer | how many days back you want to search the logs | an integer; will be converted to a negative number automatically | -7 |
| @start_date | datetime | if you want to search a specific time frame | a datetime value | NULL |
| @end_date | datetime | if you want to search a specific time frame | a datetime value | NULL |
| @custom_message | nvarchar | if you want to search for a custom string | something specific you want to search for. no wildcards or substitions. | NULL |
| @custom_message | nvarchar | if you want to search for a custom string | something specific you want to search for. no wildcards or substitutions. | NULL |
| @custom_message_only | bit | only search for the custom string | NULL, 0, 1 | 0 |
| @first_log_only | bit | only search through the first error log | NULL, 0, 1 | 0 |
| @language_id | integer | to use something other than English | SELECT DISTINCT m.language_id FROM sys.messages AS m ORDER BY m.language_id; | 1033 |
Expand Down
Loading