Explain why DBCC SHRINKFILE can take hours, monitor percent_complete and waits, and use TRUNCATEONLY before small steps.
Why Table Size Numbers Disagree: Reserved, Used and Unused Space
Reconcile table size reports by reading reserved, used, data, index, and unused pages from sys.dm_db_partition_stats on SQL Server.
Maintaining SharePoint Content Databases: What the DBA Still Owns
Review SharePoint content databases for CHECKDB, backup history, log growth, recovery model, and a tested site-collection restore.
Ordering a Maintenance Window: Backups, CHECKDB and Index Work
Order a maintenance window by listing Agent schedules, separating CHECKDB, backups, index work, and statistics, then tracking growth.
Statistics Histograms Explained
Statistics histograms explained through steps, RANGE_ROWS, EQ_ROWS, and DBCC SHOW_STATISTICS help connect data shape to plan estimates.
SQL SERVER – Shrinking Database is Bad – Increases Fragmentation – Reduces Performance
Shrinking database is bad: it increases fragmentation and reduces performance. Here is a simple example with two tables that shows it step by step.
SQL SERVER – Shrinking Database NDF and MDF Files
Previously, I had written a blog post about SQL SERVER. I am posting this blog post here about Shrinking Database.