Post reply

Push replication with distributor - any impact of rolling back transaction inserts on subscriber?

  • July 7, 2017 at 8:41 am

    #402259

    If I run SQL inserts on the subscriber but within a BEGIN TRANSACTION...ROLLBACK TRANSACTION block on will this have any adverse impacts?  Does it affect the publisher at all?  Thanks!

  • July 7, 2017 at 8:59 am

    #1949950

    No.  Changing the data on the subscriber is not an uncommon requirement.
    The issues you may face would be that transactions from the publisher would fail.  Identity fields are good examples. If you insert ID 100, 101, and so forth, the publisher may try to insert the same values and they will fail.  

    The question I have is why? It sounds like there may be a better way to approach this, if you can provide more details.

    Michael L John
    If you assassinate a DBA, would you pull a trigger?
    To properly post on a forum:
    http://www.sqlservercentral.com/articles/61537/

  • July 7, 2017 at 9:07 am

    #1949956

    Thanks for the response.  I sometimes need to run a long insert/update just to see how long it takes to know if I can run it during work hours or if I have to run it when users are out of the system.  So, I typically do the insert/update on one of our replicated servers but roll the transaction back.

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

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