Post reply

In Replication why we should not give write permission on subscribers

  • July 9, 2014 at 1:57 am

    #288508

    Hi friends,

    In our environment we have uni directional transactional replication setup.

    if we give read write access to the user on subscription databases what will happen

    and why we should not give rite waccess.

    Thanks in advance

    Regards

    Sam

    Regards,
    SAM
    ***Share your knowledge.It’s a way to achieve immortality----Dalai Lama***

  • July 9, 2014 at 11:12 am

    #1728160

    If you give write access to a subscriber changes made on the subscriber never make it to the publisher and it also will put replication out of sync. If you want to be able to write to both ends you need to look at merge or peer to peer replication.

    Jack Corbett
    Consultant - Straight Path Solutions
    Check out these links on how to get faster and more accurate answers:
    Forum Etiquette: How to post data/code on a forum to get the best help
    Need an Answer? Actually, No ... You Need a Question

  • July 9, 2014 at 9:50 pm

    #1728250

    Hi Jack,

    Thanks for prompt reply.

    Can you briefly explain how replication will be out of sync. and will break the replication or will it through any error.

    Thanks,

    SAM

    Regards,
    SAM
    ***Share your knowledge.It’s a way to achieve immortality----Dalai Lama***

  • July 11, 2014 at 9:33 am

    #1728794

    I will try to explain.

    Lets assume you have given write permission on subscriber and somebody deletes a row which is in publisher and later somebody updates that row in publisher and now distributor will try to update that row on subscriber and since that row no longer exists replication will generate an error and will stop unless you have "Continue on data consistency error option" enabled.

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

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