Replication - subscriber has own independent data

  • Hi,

    I'm new to replication and the first thing I've been asked to set up is the following scenario:

    * SQL Server A (2005 EE), in Domain A, will receive data from a custom application, and will be used locally for reporting.

    * SQL Server B (2005 EE), in Domain B, will also receive data from a custom app - but this should be separate data to the data being received by the server in Domain A.

    * The client wants the data from Server A to be replicated to Server B such that they can report on this data also.

    * Data from Server B does NOT have to be replicated to Server A.

    I was hoping to be able to setup (one way) transactional replication from Server A to Server B - does anyone have any suggestions?

    To make matters more complicated, both Server A and Server B databases will have key tables (involved in replication) partitioned. I don't know if this makes any difference to the strategy.

    Any assistance would be welcome - I can provide extra details if needed.

    Jenny

  • This is kind of a very open question. We can provide you with solutions to any problem you may encounter but replication is a very vast subject to be explained in a forum. You can start by following the wizards to setup transactional ( I presume) replication from server A to Server B. Here is an step-by-step link to get you started.

    Good Luck


    * Noel

  • SQL Server B (2005 EE), in Domain B, will also receive data from a custom app - but this should be separate data to the data being received by the server in Domain A.

    When you replicate data (to be precise, apply the snapshot from Server A) it will erase the existing data from the table. So the data received from the custom app will be lost.

    This needs to be taken care.

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

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