sp_IndexCleanup comes out of beta, Logging to tables, and Making dynamic SQL less annoying

Clear Token Perm/README.md

@@ -0,0 +1,75 @@
+<img src="https://erikdarling.com/wp-content/uploads/2025/08/darling-data-logo_RGB.jpg" width="300px" />
+
+# Clear Token Perm
+
+This directory contains scripts for monitoring and managing SQL Server's security token cache. The security token cache (TokenAndPermUserStore) can grow to a significant size in certain scenarios, potentially causing high memory usage and performance issues.
+
+## Overview
+
+SQL Server caches security tokens in memory, and in specific environments (particularly with frequent application role usage, or high numbers of users), this cache can grow to consume gigabytes of memory. These scripts provide solutions to monitor the cache size and automatically clear it when it exceeds a defined threshold.
+
+## Components
+
+The directory includes three files:
+
+1. **ClearTokenPerm.sql**: Creates a stored procedure to monitor and clear the security token cache
+2. **ClearTokenPerm Agent Job.sql**: Creates a SQL Agent job to run the ClearTokenPerm procedure on a schedule
+3. **Inflate Security Cache Demo And Analysis Script.sql**: Demonstrates how to artificially inflate the security cache for testing and provides analysis queries
+
+## ClearTokenPerm Stored Procedure
+
+The main stored procedure monitors the size of the TokenAndPermUserStore cache and clears it when it exceeds a specified threshold.
+
+| Parameter Name | Data Type | Default Value | Description |
+|----------------|-----------|---------------|-------------|
+| @CacheSizeGB | decimal(38,2) | None (required) | The threshold size in GB that triggers cache clearing |
+
+The procedure:
+- Creates a logging table (ClearTokenPermLogging) if it doesn't exist
+- Checks the current size of the TokenAndPermUserStore cache
+- Clears the cache using DBCC FREESYSTEMCACHE if the threshold is exceeded
+- Logs all checks with timestamp, cache size, and whether clearing was triggered
+
+## SQL Agent Job
+
+The Agent job script:
+- Creates a job named "Clear Security Cache Every 30 Minutes"
+- Runs the ClearTokenPerm procedure with a 1GB threshold
+- Schedules execution every 30 minutes
+- Includes error handling and transaction support
+
+## Demo and Analysis Script
+
+The demo script:
+- Creates an application role and executes a loop to inflate the cache
+- Provides detailed analysis queries to examine:
+  - Token distribution in the cache
+  - Logins and tokens per login
+  - Users and tokens per user
+  - Cache invalidations per database
+- Includes cleanup steps
+
+## Usage Examples
+
+```sql
+-- Check and potentially clear the cache if it's over 2GB
+EXECUTE dbo.ClearTokenPerm
+    @CacheSizeGB = 2;
+
+-- Query the logging table to see history
+SELECT
+    cl.* 
+FROM dbo.ClearTokenPermLogging AS cl
+ORDER BY
+    cl.log_date DESC;
+
+-- Clear the logging table
+TRUNCATE TABLE dbo.ClearTokenPermLogging;
+```
+
+## Warning
+
+The DBCC FREESYSTEMCACHE command used in these scripts will clear the security cache, which may cause a temporary performance impact as the cache is rebuilt. Test thoroughly in non-production environments before deploying to production.
+
+Copyright 2025 Darling Data, LLC  
+Released under MIT license

Helper Views/README.md

@@ -0,0 +1,104 @@
+<img src="https://erikdarling.com/wp-content/uploads/2025/08/darling-data-logo_RGB.jpg" width="300px" />
+
+# Helper Views
+
+This directory contains helper views and functions for diagnosing various SQL Server performance issues. These scripts are particularly useful for presentations and educational purposes, but can also be used in troubleshooting scenarios.
+
+## Overview
+
+The collection includes:
+- Views for analyzing index sizes
+- Functions for examining lock information
+- Views for examining memory usage
+- Procedures for testing tempdb performance
+
+## Components
+
+### WhatsUpIndexes View
+
+A view that provides detailed information about index sizes in the current database.
+
+**Functionality**:
+- Displays database, schema, table, and index names
+- Shows in-row pages size in MB
+- Shows LOB (Large Object) pages size in MB
+- Reports number of in-row used pages
+- Displays row count for each index
+- Filters out system objects and table-valued functions
+
+Usage:
+```sql
+SELECT
+    w.*
+FROM dbo.WhatsUpIndexes AS w
+ORDER BY
+    w.in_row_mb DESC;
+```
+
+### WhatsUpLocks Function
+
+A table-valued function that provides information about locks taken by specific sessions.
+
+| Parameter Name | Data Type | Default Value | Description |
+|----------------|-----------|---------------|-------------|
+| @spid | integer | NULL | Session ID to examine. If NULL, returns information for all sessions |
+
+**Functionality**:
+- Displays session ID and blocking session ID information
+- Shows lock modes, resource types, and lock status
+- Identifies locked objects and associated index names
+- Counts different lock types (HOBT, object, page, and row locks)
+- Reports total lock count
+
+Usage:
+```sql
+-- Check locks for a specific session
+SELECT
+    wul.*
+FROM dbo.WhatsUpLocks(51) AS wul;
+
+-- Check locks for all sessions
+SELECT
+    wul.*
+FROM dbo.WhatsUpLocks(NULL) AS wul;
+```
+
+### WhatsUpMemory View
+
+A view that examines what's in SQL Server memory.
+
+**Functionality**:
+- Shows database, schema, object, and index information
+- Calculates in-row pages in MB (for data types 1 and 3)
+- Calculates LOB pages in MB (for data type 2)
+- Reports total buffer cache pages
+
+Usage:
+```sql
+SELECT
+    wum.*
+FROM dbo.WhatsUpMemory AS wum
+ORDER BY
+    wum.pages DESC;
+```
+
+### tempdb_tester Procedure
+
+A stored procedure that generates semi-random tempdb activity, useful for testing and demonstration purposes.
+
+**Functionality**:
+- Creates a temporary table with approximately 10,000 rows
+- Performs various DML operations (UPDATE, DELETE, INSERT)
+- Uses RECOMPILE hint for optimal execution plans
+
+Usage:
+```sql
+EXECUTE dbo.tempdb_tester;
+```
+
+## Warning
+
+Some of these scripts (particularly WhatsUpMemory) may cause performance issues if run on busy production servers. Use with caution, especially on servers with large amounts of memory.
+
+Copyright 2025 Darling Data, LLC  
+Released under MIT license

Install-All/README.md

@@ -0,0 +1,61 @@
+<img src="https://erikdarling.com/wp-content/uploads/2025/08/darling-data-logo_RGB.jpg" width="300px" />
+
+# Install-All
+
+This directory contains tools to merge all the Darling Data stored procedures into a single installation file.
+
+## Overview
+
+Instead of installing each stored procedure individually, you can use the comprehensive DarlingData.sql file to install all procedures at once. This file is automatically generated using the Merge-All.ps1 PowerShell script.
+
+## Components
+
+1. **DarlingData.sql**: A merged file containing all stored procedures from the repository
+2. **Merge-All.ps1**: PowerShell script that generates the DarlingData.sql file
+
+## Included Stored Procedures
+
+The DarlingData.sql file includes all of the following stored procedures:
+
+| Procedure | Description | Source |
+|-----------|-------------|--------|
+| [sp_HealthParser](../sp_HealthParser) | Analyzes the system health extended event for performance information | [Link](../sp_HealthParser) |
+| [sp_HumanEvents](../sp_HumanEvents) | Makes extended events easy to use for common scenarios | [Link](../sp_HumanEvents) |
+| [sp_HumanEventsBlockViewer](../sp_HumanEvents) | Analyzes blocked process reports | [Link](../sp_HumanEvents) |
+| [sp_IndexCleanup](../sp_IndexCleanup) | Identifies unused and duplicate indexes | [Link](../sp_IndexCleanup) |
+| [sp_LogHunter](../sp_LogHunter) | Searches SQL Server error logs for important messages | [Link](../sp_LogHunter) |
+| [sp_PressureDetector](../sp_PressureDetector) | Detects CPU and memory pressure in SQL Server | [Link](../sp_PressureDetector) |
+| [sp_QuickieStore](../sp_QuickieStore) | Fast and configurable way to navigate Query Store data | [Link](../sp_QuickieStore) |
+
+## Usage
+
+### Using the Pre-Generated File
+
+Simply run the DarlingData.sql script in SQL Server Management Studio to install all stored procedures at once.
+
+### Generating a Fresh Copy
+
+If you want to generate a fresh copy of the DarlingData.sql file:
+
+1. Make sure you have PowerShell installed
+2. Navigate to the Install-All directory in PowerShell
+3. Run the script:
+
+```powershell
+.\Merge-All.ps1
+```
+
+The script will:
+1. Find all sp_* directories
+2. Skip sp_WhoIsActive directories
+3. Get all sp_* files (skipping agent job files)
+4. Combine them into a single file
+5. Add a compile date header
+6. Save as DarlingData.sql
+
+## Note
+
+The WhoIsActive Logging procedures are not included in this file, as they have a different installation process and depend on Adam Machanic's sp_WhoIsActive.
+
+Copyright 2025 Darling Data, LLC  
+Released under MIT license

Ola Stats Only Job/README.md

@@ -0,0 +1,44 @@
+<img src="https://erikdarling.com/wp-content/uploads/2025/08/darling-data-logo_RGB.jpg" width="300px" />
+
+# Ola Stats Only Job
+
+This directory contains a script to create a SQL Server Agent job for nightly statistics updates using Ola Hallengren's maintenance solution.
+
+## Overview
+
+Statistics in SQL Server are vital for query optimization but can become stale over time, leading to suboptimal query plans. This script sets up an automated job to update statistics on a regular schedule using Ola Hallengren's popular IndexOptimize stored procedure, focused specifically on statistics updates rather than the full index maintenance.
+
+## Prerequisites
+
+- Ola Hallengren's SQL Server Maintenance Solution must be installed
+  - Download from: [https://ola.hallengren.com/downloads.html](https://ola.hallengren.com/downloads.html)
+  - This script requires the version from 2018-06-16 or later, which includes the @StatisticsModificationLevel parameter
+
+## Configuration Details
+
+The script creates a SQL Agent job with the following default settings:
+- Job name: "Nightly Stats Update Job via Ola"
+- Database target: All user databases
+- Job owner: sa
+- Schedule: Every night at midnight
+- Statistics modification level: 5% (only updates statistics that have changed by at least 5%)
+
+## Customization Options
+
+You may need to modify the script to:
+- Change the target database (currently master)
+- Change the job owner from sa
+- Adjust the schedule from the default midnight run
+- Set up failure emails and alerting
+- Change the StatisticsModificationLevel from 5% to match your environment needs
+
+## Usage
+
+Simply run the script in SQL Server Management Studio after ensuring you have the prerequisites installed. The job will be created and scheduled automatically.
+
+## Note
+
+This script focuses exclusively on statistics updates. If you also need index reorganization or rebuilds, you should consider using Ola's full maintenance solution.
+
+Copyright 2025 Darling Data, LLC  
+Released under MIT license