We help IT Professionals succeed at work.
Get Started

SQL Server Compression Decision

Last Modified: 2017-04-21
I am a NUB to SQL Server, developing an Access 2013 back end DB in SQL 14.0 Developer.

I see that it is very easy to implement compression on both tables and indexes to reduce the size of the stored data.

In general I have always stayed away from compression because it adds more overhead in data, creation, retrieval and update.

My uncompressed DB size is about 100GB and we have ample disk space available to store it.  I've gone thru the compression analyzer for some of the larger tables and can see that disk requirements would be reduced by almost 65%.

The question:
Given that we have ample disk space is there any benefit to implementing compression?  If there is not a general rule about  benefit or drawbacks to using compression, what kind of criterion are used to make the decision on a table by table or even index by index level?
Watch Question
This problem has been solved!
Unlock 4 Answers and 5 Comments.
See Answers
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE