Storing E-mail addresses more efficiently in SQL Server - Part 2

In my last tip, I shared some ideas for determining if you should consider breaking up the e-mail addresses you're storing, even putting the domain names in a separate table. I performed storage and timing comparisons for working with 10,000 unique e-mail addresses, but I completely ignored data compression. I wanted to revisit the same test case and apply data compression to the tables and see how that impacted the outcome.

Page Compression in Heaps

Improving Data Compression Fidelity Without Sacrificing Speed

Making it easier to handle huge data sets

Scripts for Full DB Compression at partition level

Data compression is a key feature with SQL 2008. This script, can compress all DB objects (partition/non-partitioned) according to Partition Range you specifiy.

Data Compression: Strategy, Capacity Planning and Best Practices

The data compression feature in SQL Server 2008 helps compress the data inside a database, and it can help reduce the size of the database. Apart from the space savings, data compression provides another benefit: Because compressed data is stored in fewer pages, queries need to read fewer pages from the disk, thereby improving the performance of I/O intensive workloads. However, extra CPU resources are required on the database server to compress and decompress the data, while data is exchanged with the application. Therefore, it is important to understand the workload characteristics when deciding which tables to compress.

Data Compression