Why would I want to use Compress and Decompress functions?

  • 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

  • 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)

  • 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


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply