Re: Replication with Locked tables

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Is this on the publisher or the subscriber? The locks should only be held on
the publication database as the snapshot is being generated and on the
subscriber when the snapshot is being applied.

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

"DBAWannaB" <DBAWannaB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9EEE9100-90E0-4251-B474-384907B6C126@xxxxxxxxxxxxxxxx
> All please check me. I am working with a database and when I tried to
> replicate some of the tables I see that they are locked... I am guessing
> that
> this is because there is a previous job that drops these tables.
>
> Please help me.. is this why the tables are showing up locked when I
> attempt
> to replicate?


.

Relevant Pages

  • Re: merge: snapshot schema dependency error, advise anyone?
    ... As a quick way to troubleshoot the issue, can you setup a *snapshot* ... publication\subscription on the side with the same article schema options? ... with the bigger more complex application we need to replicate ... propagated to the subscriber. ...
    (microsoft.public.sqlserver.replication)
  • Re: merge: snapshot schema dependency error, advise anyone?
    ... It will not alter the existing objects in the subscriber if you don't want it to. ... When configuring the publication you have a few snapshot options for when the table already exist and they can be configured per article. ... tables, my concern was if I restore a full database at the client from a backup will the snapshot of the tables-only replication blow out the existing DB or will it nicely update the table portion only leaving the rest? ... the client wants to pull a snapshot before it will replicate the tables. ...
    (microsoft.public.sqlserver.replication)
  • Re: merge: snapshot schema dependency error, advise anyone?
    ... You can always take the snapshot with you and tell the subscription to find the snapshot in an alternate location. ... the client wants to pull a snapshot before it will replicate the tables. ... The schema script 'hd2_genetic_200.sch' could not be propagated to the subscriber. ...
    (microsoft.public.sqlserver.replication)
  • Re: merge: snapshot schema dependency error, advise anyone?
    ... the client wants to pull a snapshot before it will ... replicate the tables. ... propagated to the subscriber. ...
    (microsoft.public.sqlserver.replication)
  • Re: trans replication of large tables...
    ... Just because it is set to local admins doesn't mean that it can ... something as simple as a timeout during the application of the snapshot. ... subscriber, the subscription is created specifying that the subscriber ... > in the same publication - or if they are queried in the same procs they ...
    (microsoft.public.sqlserver.replication)