MS SQL Server 2008 Data Compression

by Ahlyzik M
Summary:

When implementing a database, there are a number of factors to be considered. Each factor has its own pro’s and con’s which ultimately determine what style of database will be chosen. One of the main factors involved when discussing databases is data storage, efficiency and file compression. This was a feature that Microsoft felt was important enough to be put in Microsoft SQL Server 2008. Compressing files is one of the new ways of keeping data storage small and efficient. This new feature is only in the Enterprise and Developer editions. According to the article, the data compression feature can be used on the following objects:

–          Heap Table

–          Clustered Index

–          Non-Clustered Index

–          Indexed View

–          Partitioned Table and Partitioned Index

Unfortunately, this feature of data compression will not work on row amounts more than 8060 Bytes. There are a number of commands to determine the compressed file size as well as the total amount of space saved as a result of the compression.

Reflection:

Considering the nature of business, it is essential and nearly inevitable to keep ones data efficient and up-to-date. Microsoft seems to have taken heed of this information and applied it to its most recent release of SQL 2008. I think the ability to compress data will allow for more flexibility when it comes to data storage and efficiency. Businesses will now be able to maximize their storage capacity without having to utilize 3rd party applications or make large purchases of data storage. This move by Microsoft will help businesses on multiples levels, and I await the releases that have yet to come.

Citation:

Hsu, Claire. (2011, August 16). Saving Space through SQL Server Data Compression. Retrieved from http://www.databasejournal.com/features/mssql/sql-server-data-compression.html

 

1 thought on “MS SQL Server 2008 Data Compression”

  1. Yes that is a pretty cool feature that microsoft threw into the mix. but i wonder if we want to focus on making our existing databases slightly smaller or learn how to cycle out information and not hoard it. i guess you can call data retention modern hoarding. its easy enough to do and its fairly out of mind. but still its good that microsoft is helping out the “size concious” database designer.

Comments are closed.