Why Autogrowth in Percent Slows SQL Server Down
Autogrowth in percent compounds: every growth event takes longer than the last. Here’s how to spot it and fix it before it slows down SQL Server.
Author: Steve Stedman
SQL Server Technical Debt: Where to Start Fixing It
SQL Server technical debt turns messy T-SQL into a weighted score and a cost estimate, so you know which procedure to fix first.
Why a Wide Clustered Index Costs More Than You Think
A wide clustered index gets copied into every nonclustered index on the table – here is how to find the ones actually costing you.
Who Changed the Schema? Find Out in SQL Server
See who changed the schema in SQL Server: the exact statement, login, host and application, captured by a DDL trigger you switch on per database.
Find the SQL Server Deadlock Objects That Keep Colliding
See which SQL Server deadlock objects collide with each other, on what index, under what lock mode, and which one loses every time.
Who Is Connected to SQL Server, and What They’re Doing
See who is connected to SQL Server right now, colored by state, so you can tell a connection leak from normal pooling before resizing anything.
SQL Server Signal Wait Time: The Metric Everyone Skips
Learn what signal wait time means in SQL Server wait statistics, why it signals CPU pressure, and how to read it before blaming the disk.
Reading SQL Server Trace Flags: Where to Look First
See which SQL Server trace flags on an instance are still doing anything on the current build, and which ones vanish at the next restart.
Find SQL Server Unused Indexes Before They Cost You
Find SQL Server unused indexes with sys.dm_db_index_usage_stats, see the write cost of keeping them, and get a verdict on every row.
SQL Server Full Join vs Cross Join: Key Differences Explained
When querying data in SQL Server, selecting the right join type can dramatically shape both the results and efficiency of your queries. Full Joins and Cross Joins stand out as two options that frequently lead to mix-ups, given how differently they handle data from multiple tables. A Full Join pulls every record from both tables involved, inserting NULLs wherever no match exists on the join condition. By contrast, a Cross Join creates every possible pairing of rows between the tables, …
SQL Server Full Join vs Cross Join: Key Differences Explained Read more →