Stored Procedure Generation Script
This script produces scripts for all the stored procedures in a database.
2025-06-18 (first published: 2025-06-13)
543 reads
This script produces scripts for all the stored procedures in a database.
2025-06-18 (first published: 2025-06-13)
543 reads
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
95 reads
This script will help to find orphan users on all databases and will remove them.
2025-05-20
114 reads
2025-05-06
287 reads
This script runs a SQL server Health check for services, databases, Always On, replication, CDC job status.
2025-05-05
289 reads
To fetch an execution plan from SQL Server's buffer cache (i.e., the in-memory cache of execution plans), you can query the dynamic management views (DMVs) that SQL Server exposes.
2025-04-30
77 reads
Explanation: sys.databases contains information about all databases on the SQL Server instance. • HAS_DBACCESS(name) = 1 filters out the databases you dont have access to. •ORDER BY name sorts the result alphabetically.
2025-03-04
233 reads
This script will help to get the Database mdf & ldf files size, used space, Free space in MB.
2025-02-27 (first published: 2025-02-25)
184 reads
This T-SQL script helps you monitor the size and status of all databases on your SQL Server instance, providing insights into space usage and performance.
2025-01-29 (first published: 2025-01-20)
730 reads
This procedure gets current table and index sizes of particular database and stores it to tables.
2025-01-07
232 reads
I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...
It’s been forgotten about and neglected for few years but I’ve decided to dust...
I am honored to announce that I have been renewed as a Microsoft MVP...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item Navigating Multi Platform Realities in...
I have tried a number of times to export and then import my SSMS...
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers