SQL Server Administration on SQL Server Scripts

SQL Server Object Dependencies Report: Find All References

Sat, 23 May 2026 00:00:00 +0000

Before renaming a column, retiring a view, or dropping a stored procedure, every DBA needs the answer to one question: what else depends on this object? This T-SQL script reads sys.sql_expression_dependencies and reports every referencing-and-referenced pair in the current database, with optional filtering to a single object name — the safe-refactoring impact analysis report.

Purpose and Overview

SQL Server tracks expression-level dependencies between user objects in the catalog view sys.sql_expression_dependencies. Every reference from a stored procedure, function, view, trigger, default, computed column, or check constraint to another object — table, view, function, procedure, type, or column — produces a row. The view supersedes the legacy sys.sql_dependencies view (deprecated in SQL Server 2008) and the older sp_depends stored procedure (which has always been unreliable for cross-database and late-bound references). Modern dependency tracking is metadata-only, schema-bound-aware, and accurate across cross-database name resolutions.

SQL Server Max Server Memory Calculator Script

Sat, 16 May 2026 00:00:00 +0000

Every SQL Server installation ships with max server memory set to its default value of 2,147,483,647 MB — effectively unlimited — which allows the Buffer Pool to consume all available RAM and starve the operating system of the memory it needs for network stack, disk I/O, and other critical processes. This script reads total physical RAM from sys.dm_os_sys_info, applies Jonathan Kehayias's widely-adopted OS reservation formula, and compares the recommended cap to the current sp_configure setting so DBAs can see at a glance whether action is needed.

SQL Server MAXDOP Recommendation Script

Fri, 17 Apr 2026 00:00:00 +0000

MAXDOP (max degree of parallelism) controls how many CPU threads SQL Server can use for a single parallel query. The default value of 0 allows SQL Server to use all available processors, which can cause large parallel queries to monopolise the server. This script reads the CPU topology from system DMVs and calculates Microsoft's recommended MAXDOP value for your instance.

Purpose and Overview

Setting MAXDOP incorrectly is one of the most common SQL Server configuration gaps. With MAXDOP 0 (unlimited), a single parallel query can consume every logical processor on the server, blocking other queries from getting CPU time. Setting MAXDOP too low, such as 1, disables parallelism entirely and slows down queries that benefit from parallel execution.

SQL Server Agent Job Failure History Report

Sat, 11 Apr 2026 00:00:00 +0000

Report SQL Server Agent Job Status and Failure History

This script queries the SQL Server Agent job history stored in msdb to produce a detailed report of each job's most recent run status, failure and success counts over the last 60 days, total lifetime run counts, and job step information including subsystem type and proxy name.

Purpose and Overview

SQL Server Agent jobs automate the critical work of database backups, index maintenance, integrity checks, ETL loads, and more. When a job fails, the impact can range from a missed backup to a halted data pipeline. Knowing which jobs failed, how recently they failed, and whether failures are isolated events or a recurring pattern is essential for any DBA. This script, written by Jason Brimhall and published in the ktaranov/sqlserver-kit community repository, uses a series of common table expressions to build a rich job history report. It shows the most recent outcome for each job status type, counts failures and successes within the last 60 days relative to the latest run, and includes job step details. To report only failures, uncomment one line. Run this script in the context of the msdb database.

SQL Server Kill Sessions: Filtered SPID Management

Sat, 11 Apr 2026 00:00:00 +0000

Kill SQL Server Sessions with Targeted Filters Using KILL and dm_exec_sessions

This article covers a practical T-SQL script that kills one or more SQL Server sessions (SPIDs) while giving you precise control over which sessions are targeted. The script uses sys.dm_exec_sessions to query active sessions and a cursor to issue KILL commands only against sessions that match your chosen filters.

Purpose and Overview

When you need to disconnect users from a SQL Server database — whether before taking it offline, restoring it, or clearing stuck sessions — the built-in KILL command works on one session at a time. Writing a loop to kill many sessions adds complexity. This script wraps that logic into a reusable tool with a safety switch and seven filter parameters so you can scope kills as broadly or narrowly as needed.

SQL Server Search Stored Procedure and View Text

Thu, 09 Apr 2026 00:00:00 +0000

Search Stored Procedure and View Definitions in SQL Server

This script searches the text of stored procedures, views, functions, and triggers in the current database using sys.sql_modules, returning any programmable object whose name or definition contains a given keyword.

Purpose and Overview

Finding which stored procedures, views, or functions reference a specific table, column, or keyword is a routine DBA and developer task. It comes up when renaming a column, tracking down where a piece of business logic lives, auditing who calls a particular table, or investigating the impact of a schema change. SQL Server stores the source definition of every programmable object in sys.sql_modules, making it straightforward to search across all object types in a single query. This script, adapted from the sqlserver-kit community collection by Ed Pollack and Konstantin Taranov, queries sys.sql_modules joined to sys.objects to search both object names and their full definitions, returning results with the object type, schema, and full source text.

SQL Server Error Log Search Script: xp_readerrorlog

Wed, 08 Apr 2026 00:00:00 +0000

Search the SQL Server Error Log with xp_readerrorlog

This script reads and filters the SQL Server error log using xp_readerrorlog and sys.sp_readerrorlog, supporting keyword search, date range filtering, and access to archived log files — all from T-SQL without touching the file system.

Purpose and Overview

The SQL Server error log records startup events, login failures, database state changes, backup completions, DBCC output, and any errors raised by the engine. When something goes wrong — a database goes suspect, a backup fails, or a login is repeatedly denied — the error log is the first place to look. SQL Server provides two built-in mechanisms for reading the log from T-SQL: the undocumented extended stored procedure xp_readerrorlog and its documented wrapper sys.sp_readerrorlog. Both support keyword filtering and date ranges, making them far more useful than opening the log file in SSMS's Log Viewer for scripted or automated diagnostic work. This script, adapted from the Read_errorlog.sql in the sqlserver-kit collection by Konstantin Taranov, demonstrates how to search one or more error log files efficiently from T-SQL.

SQL Server DBCC CHECKIDENT: Bulk Identity Column Analysis

Sun, 03 Aug 2025 00:00:00 +0000

SQL Server DBCC CHECKIDENT: Complete Guide to Identity Column Management and Bulk Table Analysis

Purpose and Overview

The DBCC CHECKIDENT command is a critical database administration tool in Microsoft SQL Server designed to manage and monitor identity column values. This article explores a practical implementation that demonstrates both individual table identity checking and automated bulk analysis across all user tables in a database.