Results 1 to 3 of 3

Thread: Remove data from Publisher after replication

  1. #1
    Join Date
    Jul 2010
    Posts
    2

    Post Remove data from Publisher after replication

    Hi folks,

    Currently, transactional replication with updatable subscription is configured on our web application so that data will be replicated from "external" DB to "internal" DB and vice versa. We are now thinking whether it is possible to remove the data from the "external" DB as much as possible to reduce the rick of being hacked and lost sensitive data from it. Is there any option in replication can achieve this? Or should it be done in a way other than replication?

    Thanks in advance.

    Kenneth

  2. #2
    Join Date
    Sep 2002
    Posts
    5,938
    When the table is replicated like this case, deleting rows on one side will be replicated to the other side (means delete on both side). Two-way replication is not good choice if you want table holds different rowset on each side.

  3. #3
    Join Date
    Jul 2010
    Posts
    2
    You are right Rmiao, that's the problem that need to be tackled. Simply speakly, we need to remove data from "external DB" after replicating to "internal DB".

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •