Database File Growth Report Script
A T-SQL script to track and monitor the growth of your SQL Server Databases.
2025-09-12 (first published: 2025-09-04)
286 reads
Scripts
Index Efficiency & Maintenance Advisor
This script will help DBAs to find inefficient indexes and duplicate indexes, by providing the following metrics: usage statistics, fragmentation levels, size, and index duplication analysis.
2025-09-10 (first published: 2025-06-27)
272 reads
Enables Change Data Capture (CDC) on all user databases
This script loops through all user databases, skips system DBs and any you want to exclude, and enables CDC if it’s not already enabled.
2025-09-05 (first published: 2025-08-25)
412 reads
Free T-SQL Script: Database Schema Documentation Generator for Generative AI Services Integration
This script automatically generates comprehensive schema documentation that can be easily consumed by AI services for natural language querying, automated report generation, and intelligent data analysis.
2025-09-03 (first published: 2025-08-25)
730 reads
Fetch fields like email address from multiple records into single cell
COALESCE smartly helps to concatenating the multiple rows value into one cell.
2025-09-01 (first published: 2025-08-25)
1,460 reads
Cleanup backup file folder future 7 days
Two PowerShell scripts to create backup folders and clean up old files.
2025-08-29 (first published: 2025-08-16)
200 reads
Stored Procedure Generation Script
This script produces scripts for all the stored procedures in a database.
2025-06-18 (first published: 2025-06-13)
783 reads
T-SQL Table Valued Function to compare Semantic Versions
Semantic versioning (SemVer) is a standardized system for labeling software releases using a three-part number—major, minor, and patch—optionally followed by pre-release labels and build metadata. Comparing semantic versions is complex because it requires handling both numeric and string components, as well as special precedence rules for pre-releases and stable versions. SQL Server’s hierarchyid data type is ideally suited for comparing the numeric parts of semantic versions, enabling efficient and accurate ordering without the pitfalls of string comparison or manual parsing.
2025-05-27
167 reads
Script-Drop Orphan users from SQL Server Database
This script will help to find orphan users on all databases and will remove them.
2025-05-20
242 reads
2025-05-06
528 reads
Blogs
SQL Saturday Boston Slides and Code
By Steve Jones
Thanks to everyone who attended my sessions today at SQL Saturday Boston 2025. I’ve...
Scaling SQL Server 2025 Vector Search with Load-Balanced Ollama Embeddings
SQL Server 2025 introduces native support for vector data types and external AI models....
Advice I Like: Fear and Imagination
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
Forums
How to use data pre-computed in previous ETL SSIS Nodes?
I'm building ETL packages in SSIS. My data comes from an OLE DB Source...
Building AI Governance and Policies- First Steps
Comments posted to this topic are about the item Building AI Governance and Policies-...
Simple delete causes table scan on other tables with foreign key
Why is sql doing a full scan VS seeking on the index? I've included...
Question of the Day
Checking Identities
The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:
TravelLogID CityID StartDate EndDate 1 1 2025-01-11 2025-01-16 2 2 2025-01-11 2025-01-16 3 3 2025-01-11 2025-01-16 4 4 2025-01-11 2025-01-16 5 5 2025-01-11 2025-01-16 6 6 2025-01-11 2025-01-16 7 7 2025-01-11 2025-01-16 8 8 2025-01-11 2025-01-16 9 9 2025-01-11 2025-01-16 10 10 2025-01-11 2025-01-16The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9
GO
DBCC CHECKIDENT(TravelLog, RESEED)
GO
INSERT dbo.TravelLog
(
CityID,
StartDate,
EndDate
)
VALUES
(4, '2025-09-14', '2025-09-17')
GO
What is the identity value for the new row inserted by the insert statement above? See possible answers