Post reply

In SQL 2008 R2, does Database Mirroring allow you to persist a compressed object to the target Mirror?

  • October 17, 2013 at 10:15 am

    #281581

    In SQL 2008 R2, if I use data compression on Server_A, Database_A, Table_A and compress a 20 GB table down to 5 GB -- then setup Database Mirroring (endpoints) to mirror the database to Server_B, will the data compression persist? On the Mirror, will this table be 20 GB or 5 GB?

    (I now in SQL 2008 R2 snapshot & transactional replication, there is a property called 'COPY DATA COMPESSION ATTRIBUTE' which you can set to YES (per article or for all articles) persist your compressed data to subscribers)

    BT

  • October 17, 2013 at 10:41 am

    #1659409

    Yes.

    So the way mirroring works is that you'll move a full backup over to the secondary. So that if you restore it, compression will be enabled. This means you need the same edition on the other side to support this. All other commands, like compression added to indexes, will be sent to the secondary.

  • October 17, 2013 at 12:19 pm

    #1659450

    A mirror is an exact copy of the principal database in very way.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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