SQL Server Performance

Replication issue

Discussion in 'Performance Tuning for SQL Server Replication' started by ajjee, Mar 29, 2006.

  1. ajjee New Member


    Our publication database is around 30GB, every time there is a problem with the replication and we have to take the snapshot of replication for our subscriber. we have to wait for 2 days for 30 GB to transfer across, My question is is:

    1- can we restore the backup of a database at the subscriber's side and synchronise the data to save alot of time.

    2-our publication has got more then 50 very large tables if during the snapshot process there is some sort of error the whole thing starts again from the begining, is there a way to carry on from that point and onwards only.



  2. jv@sepia.be New Member

    Is it necessary to take a snapshot ? Can you not use transactional or merge ?
  3. satya Moderator

    https://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx fyi and study.


    Satya SKJ
    Microsoft SQL Server MVP
    Contributing Editor & Forums Moderator
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  4. ndinakar Member

    You can restore the db over at the subscriber and configure it. We did it for 150 GB db in less than 30 minutes.

    Dinakar Nethi
    Life is short. Enjoy it.

Share This Page