What will be impace of doing Snapshot Replication

  • Hi All,

    I have a databases A . I am doing Snapshot replication for Creating one more database B. While doing Snapshot replication what will be the impact of the tables in source database (A)? What i mean is,

    how long the tables in database A will be locked position? If all the tables in the database A is locked for some time say, 5 min, how to handle the requests comming to A while the database is in locked postion? If any one knows about this ..please help me..

    Thanks in Advance,

    Sarat.

  • The Main problem with Snapshot is that it will cause dead locks. You want to create a Subscriber using Snap shot replication? That might work if you have a very small DB. If you have a large DB, then this could cause big problems.

    Let us consider that the snap shot is scheduled to happen at 6 AM. Your DB is stioll being used at that time. This could mean that the Snap Shot might get dead lock issues and fail to complete or render the whole DB inaccessable for period of time.

    Why not go for transactional replication. You have to worry about Dead locks only once. That is when intializing the Rep0lication. After that you wont see any Dead lock scenarios because you have replication.

    Just my 2 cents

    -Roy

  • IF you have enterprise edition you can select "database snapshot" for snapshot type It WONT lock the tables extensively like native mode does. If you don't have Enterprise Edition you could do "concurrent snapshot" and it won't lock the tables extensively either.

    Good Luck,


    * Noel

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

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