troubleshooting Question

SQL Server Compression Decision

Avatar of mlcktmguy
mlcktmguyFlag for United States of America asked on
Microsoft AccessMicrosoft SQL Server
5 Comments4 Solutions165 ViewsLast Modified:
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?
SOLUTION
Snarf0001

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 4 Answers and 5 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 4 Answers and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros