SQL Server Performance

Warm standby server

Discussion in 'SQL Server Log Shipping' started by TerryCrosby, Jan 20, 2004.

  1. TerryCrosby New Member

    We want to establish a warm standby for our production database (SQL 2K sp3, approx. 170GB in size). Which would be the better method to accomplish this, log shipping or publish/subscribe? This will be my first attempt at a warm standby so any suggestions, even if different from mine would be greatly appreciated. Thanks.

    Terry Crosby
  2. Luis Martin Moderator

  3. Twan New Member

    HI ya,

    it depends...

    log shipping is easy to implement, and works irrespective of the database design, and has a longer lag time, but is more expensive if you use the MSSQL logshipping.

    replication is more difficult to implement and may require application/design changes, can be near-real time but can run on Std Edition of SQL Server

    Cheers
    Twan
  4. satya Moderator

  5. TerryCrosby New Member

    Satya, this page cannot be found. Could you report?

    Terry Crosby
  6. satya Moderator

    Thanks, I've corrected my post above with proper link.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  7. strongsad New Member

    Near-topic question: Would you recommend log shipping if the target database is not meant to be a backup, but rather is a production, heavily read (read-only) database? The schema will not change, I don't need users or other objects, I only need 3 tables (not the whole db).

    To me, replication seems to make more sense for this scenario, but my dba's are saying replication would be too much work, and they want to do log shipping. However, I have easily implemented this type of one-way replication successfully using the much-improved SQL 2000 replication wizards.

    Opinions?

    -Allen
  8. satya Moderator

    I would go with your DBA's choice, replication is more of work as compared to the log shipping process.

    But if you're comfortable with your method then ensure no issue arises, follow the above link for log shipping process information.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  9. bradmcgehee New Member

    Log shippping is the easiest way. I know from experience.

    -----------------------------
    Brad M. McGehee, MVP
    Webmaster
    SQL-Server-Performance.Com

Share This Page