SQL Server Performance

Looking for a way to add a second subscriber without snapshot

Discussion in 'SQL Server 2008 Replication' started by WingSzeto, Oct 14, 2009.

  1. WingSzeto Member

    We are currently replicating a database (70G) from SQL 2008 std (server A) to SQL 2005 std (server B). We are using transactional and push method. The distributor db and publisher db are on the same server (server A). To create the second subscriber on a different SQL 2005 std computer(server C), I did the following steps:
    1. stop the log reader on the publisher and the sync process on the subscriber
    2. Make some data changes on the publisher db on server A (for testing purpose).
    3. do a backup of the subscriber in server B, and restore it to server C.
    4. Create subscriber for server C using the replicatin wizard and generate the creation script. Then change the sync method to 'replication support only'.
    5. start log reader and the sync process for both subscribers.
    When I test these steps, Any data changes made on the publsihed db on server A (step 2) during the log reader down time are not replicated to server B and C when step 5 is executed. Does this make sense or I did something wrong? Are there other requirements for this process to work? I could use snapshot but time is limited.
  2. Nirav.J New Member

    YEs we can certainly perforn this scenario withoit any problem Its tested
  3. satya Moderator

    Sounds like a plan and it should do the rest.

Share This Page