Merge pull request #3865 from BrentOzarULTD/3864_sp_kill

Add sp_kill stored procedure (#3864)

Author: BrentOzar

README.md

@@ -19,10 +19,11 @@ Navigation
    - [sp_BlitzFirst: Real-Time Performance Advice](#sp_blitzfirst-real-time-performance-advice)
    - [sp_BlitzIndex: Tune Your Indexes](#sp_blitzindex-tune-your-indexes)
      - [Advanced sp_BlitzIndex Parameters](#advanced-sp_blitzindex-parameters)
- - Performance Tuning:   
-   - [sp_BlitzLock: Deadlock Analysis](#sp_blitzlock-deadlock-analysis) 
-   - [sp_BlitzWho: What Queries are Running Now](#sp_blitzwho-what-queries-are-running-now)   
-   - [sp_BlitzAnalysis: Query sp_BlitzFirst output tables](#sp_blitzanalysis-query-sp_BlitzFirst-output-tables) 
+ - Performance Tuning:
+   - [sp_BlitzLock: Deadlock Analysis](#sp_blitzlock-deadlock-analysis)
+   - [sp_BlitzWho: What Queries are Running Now](#sp_blitzwho-what-queries-are-running-now)
+   - [sp_kill: Emergency Session Killer](#sp_kill-emergency-session-killer)
+   - [sp_BlitzAnalysis: Query sp_BlitzFirst output tables](#sp_blitzanalysis-query-sp_BlitzFirst-output-tables)
  - Backups and Restores:
    - [sp_BlitzBackups: How Much Data Could You Lose](#sp_blitzbackups-how-much-data-could-you-lose)  
    - [sp_DatabaseRestore: Easier Multi-File Restores](#sp_databaserestore-easier-multi-file-restores)  
@@ -331,6 +332,61 @@ It's designed for query tuners, so it includes things like memory grants, degree
 [*Back to top*](#header1)
 
 
+## sp_kill: Emergency Session Killer
+
+When the server is on fire and you're about to restart it out of desperation, run sp_kill instead. It collects all running session data, recommends which queries to kill (with reasons), optionally executes the kills for you, frees their plan cache entries, and logs everything.
+
+By default, sp_kill runs in read-only mode - it just shows you what's happening and suggests what to kill. You have to explicitly opt in to actually killing sessions.
+
+```tsql
+/* Just show me what's running - no killing: */
+EXEC sp_kill;
+
+/* Kill all lead blockers: */
+EXEC sp_kill @LeadBlockers = 'Y', @ExecuteKills = 'Y';
+
+/* Kill a specific session: */
+EXEC sp_kill @SPID = 55, @ExecuteKills = 'Y';
+
+/* Kill sleeping sessions with open transactions idle for 5+ minutes: */
+EXEC sp_kill @HasOpenTran = 'Y', @SPIDState = 'S',
+    @RequestsOlderThanMinutes = 5, @ExecuteKills = 'Y';
+
+/* Show what we'd kill for a login, sorted by CPU: */
+EXEC sp_kill @LoginName = 'DOMAIN\TroublesomeUser', @OrderBy = 'cpu';
+```
+
+Parameters for targeting sessions:
+
+* @ExecuteKills = 'Y' or 'N' (default 'N') - whether to actually kill, or just show recommendations. When set to 'Y', you must also specify at least one targeting filter to prevent accidentally killing everything.
+* @SPID - target a specific session ID.
+* @LoginName - kill sessions belonging to this login.
+* @AppName - kill sessions from this application (supports LIKE wildcards).
+* @DatabaseName - kill sessions using this database.
+* @HostName - kill sessions from this host.
+* @LeadBlockers = 'Y' - kill only lead blockers (sessions blocking others but not blocked themselves).
+* @ReadOnly = 'Y' - only kill read-only queries (SELECTs with no writes).
+* @SPIDState - 'S' for sleeping sessions only, 'R' for running only, empty string for both (default).
+* @HasOpenTran = 'Y' - only target sessions with open transactions. Combine with @SPIDState = 'S' to catch sleeping sessions with forgotten transactions.
+* @RequestsOlderThanMinutes - only target sessions whose last request started at least this many minutes ago.
+* @OmitLogin - exclude sessions belonging to this login from kill recommendations.
+* @OrderBy - sort order for kill recommendations: duration (default), cpu, reads, writes, tempdb, transactions. Useful when you want to kill the worst offenders one by one.
+
+Safety features:
+
+* Never kills system sessions (session_id <= 50) or its own session.
+* Never kills sessions that are already rolling back.
+* Before each kill, verifies the session still has the same query it had when captured. If the query changed (because the original finished and a new one started on the same session ID), the kill is skipped.
+* Frees the plan cache entry for each killed query via DBCC FREEPROCCACHE.
+* When @ExecuteKills = 'Y', shows progress messages like "Killing query 3 of 12 (SPID 78)..." so you can follow along.
+
+Output table logging:
+
+* @OutputDatabaseName, @OutputSchemaName, @OutputTableName - pass all three to log results to a persistent table. The table is created automatically if it doesn't exist, and each run appends new rows. Includes who ran sp_kill, when, what parameters they used, what sessions were running, which ones were killed, and any errors.
+
+[*Back to top*](#header1)
+
+
 ## sp_BlitzAnalysis: Query sp_BlitzFirst output tables
 
 Retrieves data from the output tables where you are storing your sp_BlitzFirst output.

Uninstall.sql

@@ -28,7 +28,8 @@ SELECT 'sp_BlitzQueryStore' as ProcedureName UNION
 SELECT 'sp_BlitzWho' as ProcedureName UNION
 SELECT 'sp_DatabaseRestore' as ProcedureName UNION
 SELECT 'sp_foreachdb' as ProcedureName UNION
-SELECT 'sp_ineachdb' as ProcedureName
+SELECT 'sp_ineachdb' as ProcedureName UNION
+SELECT 'sp_kill' as ProcedureName
 
 --End Variables