Pros and cons of doing replication and log shipping together

  • My requirements -

    Setting up stand by database using log shipping for Disaster recovery, this database will act as my DR database.

    At the same time i want to setup replication for read only database for operations needs at remote site.

    Questions

    is it possible?

    pros and cons of this setup?

  • Not possible.

    Log shipping will put the db in read only mode, so replication won't be able to apply changes at the subscriber.

    With log shipping, you can have both things. You will have a server for disaster recovery and the db will be in read only mode.

     

     

  • i didn't phrase the question properly.

    Let me put this way.

    I want log shipping and replication both from primary production database. One for standby(DR) and one for replication(read only db)

    Primary Database(proddb) ==log shipping == standby db(prodstdby)

    Primary Database(proddb) ==replication == read only (prodread)

    what are the pros and cons of this kind of steup

  • Ih that way I think you can.

    But it will be difficult to set up a read only server with replication.

    Everytime the replication is done, you will have to pub your db in a non read only mode, to allow replication.

    You can also limit only to select transactions managin permissions with users.

  • log shipping and replication are going to two different databases

Viewing 5 posts - 1 through 4 (of 4 total)

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