April 4, 2020 at 2:44 pm
in what live operational or development situation /requirement would I want to use the Compress function?
like when should i become thankful for Compress and Decompress functions introduced in version 2016?
Likes to play Chess
April 4, 2020 at 3:10 pm
for example when you have varchar max columns that compress very well (like email body (without attachments) and those columns will never be subject to a search.
in one of my db's that is what I did to the email archive table - size went down from 1 TB to 300GB. (although I did use a inhouse CLR for compression as I implemented this in SQL 2008R2 - but had we been on a version that had compress I would have used it instead)
April 4, 2020 at 8:03 pm
It's also great for the archival of data. Please see "Example B" at the following link.
https://docs.microsoft.com/en-us/sql/t-sql/functions/compress-transact-sql?view=sql-server-ver15
It could also be an easy way to ZIP such data for data transmission files.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy