Post reply

Log Shipping with Compression

  • May 17, 2012 at 7:35 am

    #256644

    Hi All

    Has anyone experienced any issue with running Log Shipping with Compression turned on?

    I know that there is a bit of a CPU overhead when using this feature, I wanted to know if there is any other caveats I should be aware of

    Thanks

  • May 17, 2012 at 9:16 am

    #1489098

    I haven't used it, but compression in terms of row/data is fairly minimal load. You will be reading the logs, compressing the data, and sending it off.

  • May 17, 2012 at 11:45 am

    #1489266

    Steve Jones - SSC Editor (5/17/2012)

    I haven't used it, but compression in terms of row/data is fairly minimal load. You will be reading the logs, compressing the data, and sending it off.

    Thanks

    Just want to be sure before implementation.

  • May 17, 2012 at 1:16 pm

    #1489319

    Steve Jones - SSC Editor (5/17/2012)

    I haven't used it, but compression in terms of row/data is fairly minimal load. You will be reading the logs, compressing the data, and sending it off.

    As a more recent inductee into the World of SQL Server, I've been learning that cool features, the why isn't everyone using it kind of features comes at a Price, Limitation, Drawback etc....

    I'm trying to figure out what that Price, Limitation, Drawback is with the backup compression feature, besides the CPU cost.

    Unless of course, the CPU cost is REALLY considerable

  • May 17, 2012 at 2:52 pm

    #1489372

    Backup compression isn't available in every edition of SQL Server.

    The CPU cost is the main thing, and it's not horrible, but it depends on when you do it and when your load.

  • May 17, 2012 at 11:50 pm

    #1489483

    Steve Jones - SSC Editor (5/17/2012)

    Backup compression isn't available in every edition of SQL Server.

    The CPU cost is the main thing, and it's not horrible, but it depends on when you do it and when your load.

    Thanks

    We Ship every 15 mins and restore every 24 hours

  • May 18, 2012 at 10:26 am

    #1489816

    The load would be when your backups run on the primary. What is the workload like?

    Check basic perfmon (CPU, pages/sec, disk IO) while people are working, and then when the backup runs.

    Try it with and without compression. See if there is an impact.

  • May 19, 2012 at 10:50 am

    #1490137

    Compression of log backups is very minimal. The CPU cost of compression is mostly balanced out by the reduced cost of IO (which is also CPU).

    My blog: SQL Soldier[/url]
    SQL Server Best Practices:     SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

Viewing 8 posts - 1 through 7 (of 7 total)

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