Log Shipping for Reporting

• timwam

  SSC-Addicted

  Points: 477

  More actions

  September 27, 2010 at 9:32 am

  #224434

  Hi,

  We're contemplating using log shipping for a warm standby and reporting solution. I'm happy with the limitations around single-user access during restores, and the prospect of large log files when we reorganise tables on the primary server.

  My question is - if you do perform a reorg on a table in the master, do the logs that get produced actually reorganise the index on the log-shipped secondary? One would hope that the large logs produced would be of some benefit at the other end! I would not want the reporting performance to degrade over time. Can't find anything that addresses this.

• george sibbald

  SSC Guru

  Points: 104210

  More actions

  September 27, 2010 at 3:33 pm

  #1228056

  yes it does.

  All the page moving that reindexing does is recorded in the log so is therefore replayed on the secondary database.

  Just the same as if you restored a database and followed that by restoring tran logs that rolled through an index rebuild, you would expect to end up with a database that reflects ALL activity up to that point.

  ---------------------------------------------------------------------