Design Supplier data

  • hi All,

    I have a Supplier data :

    COMPARE:

    SERVER A : V, SERVER B : V, ACTION : UPDATE

    SERVER A : V , SERVER B : --, ACTION : ADD

    SERVER A : -- (deleted), SERVER B : V , ACTION : ?

    SERVER A : V (Value), SERVER B : V , ACTION : Update

    If server A is a Source and Server B is the Mirror Server, How I could manage the data if there is any deleted accidentally data at the Source but still exists at Server B ?

    while its data is important and should not be deleted ?

    I need advice please

  • Deny Christian (11/7/2016)


    hi All,

    I have a Supplier data :

    COMPARE:

    SERVER A : V, SERVER B : V, ACTION : UPDATE

    SERVER A : V , SERVER B : --, ACTION : ADD

    SERVER A : -- (deleted), SERVER B : V , ACTION : ?

    SERVER A : V (Value), SERVER B : V , ACTION : Update

    If server A is a Source and Server B is the Mirror Server, How I could manage the data if there is any deleted accidentally data at the Source but still exists at Server B ?

    while its data is important and should not be deleted ?

    I need advice please

    I think that before looking at a synchronization etc. one should focus on the actual problem which seems to be unauthorized data modification, in most cases preventable using roles, permissions and even DML blocking triggers.

    😎

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

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