This blog post will explore three underused features that can significantly enhance your SQL Server experience. Let us discuss 3 Underutilized Features.
Compressed and Uncompressed Backup: One Script, One Switch
A compressed and uncompressed backup differ by one word. This post puts COMPRESSION and NO_COMPRESSION in one script with a switch, compares size and time, and shows that the restore statement is the same for both.
Data Compression for Performance – SQL in Sixty Seconds #188
Earlier I wrote a blog post about how Data Compression for Performance can help improve the efficiency of SQL Server.
Estimate Compression Savings for Every Table in a Database
To estimate compression savings for every table, loop over the database and call sp_estimate_data_compression_savings with ROW and PAGE. This post ranks tables by space saved and checks one estimate against a real rebuild.
SQL SERVER – Data and Index Compression – Real-World Conversation
Index Compression needs workload measurements of storage, I/O and CPU. A customer conversation prompted my earlier advice.
How Much Space Does a NULL Take? NULL Storage in Rows
Measure NULL storage in ordinary rows, compare fixed and variable columns, inspect record size, and test sparse and compressed designs.
Page and Row Compression in SQL Server: Estimate, Enable, Remove
Page and row compression shrink a table or index, and each one is a single ALTER statement. This post estimates the savings first, turns each level on and off in a demo, and measures what the page rebuild costs in CPU.