Post reply

Locking the replicated table on the subscriber after bcp of re-initializing

  • May 25, 2011 at 3:52 am

    #96204

    Hi All,

    When re-initializing a subscription, once the bcp has been done why is the replicated table on the subscriber locked? Also, as it is moving through the replicated commands when it comes accross one for the table that has just been replicated it is taking around 30 - 60 seconds for the ins / del to occurr.

    Is this the norm? How do I know when the lock will be release from the replicated table on the subscriber?

    Cheers,

    Gary

  • May 25, 2011 at 4:29 am

    #1329576

    A bit more info, from what I can see via the Profiler, once it has bcp'd the data it then inserts quite a bit of data before it decides to create the indexes, why doesn't it just create the index straight after the bcp?

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

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