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.
Author: Steve Stedman
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 →
SQL Server Historic Reporting: One Page, One Click
See SQL Server historic reporting in one place: plan cache hit ratio, page life expectancy, CPU, deadlocks, and file growth, trended together.
SQL Server Backup and Recovery Course
In the wise words of Benjamin Franklin, “If You Fail to Plan, You Are Planning to Fail.” This timeless adage holds particular relevance when it comes to safeguarding your SQL Server databases. A failure to adequately prepare for data loss scenarios—be it due to hardware malfunctions, data corruption, or increasingly prevalent ransomware attacks—can have devastating consequences for your business. The Common Problem: Lack of Preparedness Despite the rising risks, it’s shocking how often we encounter businesses that are inadequately prepared …
SQL Server TempDB Allocation: What’s Actually Filling It
SQL Server tempdb allocation splits into three bands, so a full tempdb points to code, a bad plan, or a long transaction instead of a guess.