Data Manipulation on Read Only subscribers

  • Hi Friends,

    Although the situation is not too tricky on its face but would request some feedback for implementing a correct approach.

    I have a transactional replication for reporting purpose and subscriber are meant only for read-only operations. The distribution agent is the only login that should write the data. However, I have witnessed

    that at times somehow some data goes missing on subscriber side and then replication alerts give an error message: ' row not found on subscriber'

    At one instance, I could find that one of my colleagues ran a DML script meant for publisher(OLTP side).

    Is there a way to track 'who, what and when' on subscriber side to catch this. There are some people who has got access(authorized and un-authorized) and to make the approach more disciplined, I need to implement some sort of tracking on my databases.

    Thanks

    Chandan Jha

Viewing 0 posts

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