Rows versus size decides which tables are huge in SQL Server. One query reads sys.dm_db_partition_stats and ranks every table twice, by rows and by size. A demo shows 300 rows that outweigh 300,000 rows, and why the older join misleads.
SQL SERVER – Check Backup Reliability
Backup Reliability needs a successful restore followed by integrity and application validation. Customers ask whether they can skip that exercise.
SQL SERVER – Finding Fragmentation in Forwarded Records
Finding Fragmentation in a heap also requires a separate check for forwarded records. I measure their effect before choosing maintenance.
SQL SERVER – Who Dropped Table? Part 2
A dropped table can leave transaction-log clues, but those clues are not a complete audit trail. My original investigation had limits.
Running Totals That Reset Every Month
Calculate running totals that reset by calendar month, customer, or fiscal period, using stable ordering and explicit ROWS frames.
Before You KILL a Session: Estimating the Rollback Cost
Before you KILL a session, inspect its transaction age, log bytes, current command, and likely rollback work, then monitor the undo safely.
Hide Code in SSMS – SQL in Sixty Seconds #154
I have received so many emails from all of you to create a video on the topic of SQL SERVER – Hide Code in SSMS. Here is the video on the topic.