Push Subscription - will it overwrite existing data first?

If I push a new subscription to an existing target database, and I choose or
check the box to include schema and data, will replication first delete or
empty tables at the target before pushing a new?
I did this, that is to push the subscription and checked the box to send
schema and data and killed the process mid-stream. At the target I found
certain tables to be empty. I am concluding that replication will first
empty or delete tables at the target.
Am I correct?
thanks,
bob
Bob,
on the article properties of a table, on the snapshot tab there is the
option to control this behaviour. By default if you look at the bcp files
per article, they will start with a drop table then a create table and after
that the rows will be inserted. It looks like you caught the process in
between these batches.
HTH,
Paul Ibison

publisher malfunction

Hi,
Has anyone seen a problem like this:
when trying to add an article to an existing publication (i.e. running
sp_addarticle) I get the following error if I run it from my workstation:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
the error is a bit more descriptive when running from the server console:
Server: Msg 8526, Level 16, State 2, Procedure sp_helpdistributor, Line 79
Cannot go remote while the session is enlisted in a distributed transaction
that has an active savepoint.
Connection Broken
Any input would be appreciated
run a dbcc opentrans and see if there is an open or orphaned transaction.
use dbcc inputbuffer to evaluate whether you can kill it or not. If so, kill
it and try to run the sp_addarticle command again.
Also is this with a remote distributor?
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
"Mor DeRor" <MorDeRor@.discussions.microsoft.com> wrote in message
news:55DBD5B3-15F1-4130-8BB8-F3B2FA7294BC@.microsoft.com...
> Hi,
> Has anyone seen a problem like this:
> when trying to add an article to an existing publication (i.e. running
> sp_addarticle) I get the following error if I run it from my workstation:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> the error is a bit more descriptive when running from the server console:
> Server: Msg 8526, Level 16, State 2, Procedure sp_helpdistributor, Line 79
> Cannot go remote while the session is enlisted in a distributed
> transaction
> that has an active savepoint.
> Connection Broken
> Any input would be appreciated
|||Thanks Hilary, but it does not look like there is an open transaction. here
is the oputput of DBCC OPENTRAN:
Replicated Transaction Information:
Oldest distributed LSN : (2215838:4377:1)
Oldest non-distributed LSN : (0:0:0)
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
"Hilary Cotter" wrote:

> run a dbcc opentrans and see if there is an open or orphaned transaction.
> use dbcc inputbuffer to evaluate whether you can kill it or not. If so, kill
> it and try to run the sp_addarticle command again.
> Also is this with a remote distributor?
> --
> 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
>
> "Mor DeRor" <MorDeRor@.discussions.microsoft.com> wrote in message
> news:55DBD5B3-15F1-4130-8BB8-F3B2FA7294BC@.microsoft.com...
>
>
|||I found a solution, in case anyone else is interested. It had to do with
"remote proc trans" option being turned on. Here is a link to the forum where
I found it:
http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=18530
"Mor DeRor" wrote:
[vbcol=seagreen]
> Thanks Hilary, but it does not look like there is an open transaction. here
> is the oputput of DBCC OPENTRAN:
> Replicated Transaction Information:
> Oldest distributed LSN : (2215838:4377:1)
> Oldest non-distributed LSN : (0:0:0)
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>
> "Hilary Cotter" wrote:

Publication Filter Clause changes

Hello,
I've merge replication set between SQL Server 2000 & SQL CE.
Whenever I try to add filter clause to the existing publication, it gives
error mentioning the column name used in the filter clause.
Ex. Let's say I've 5 publications - Pub1, Pub2, Pub3, Pub4, Pub5.
If I add filter clause say 'Employee_Status <> 0' then it throws the error
as 'Invalid Column Name 'Employee_Status'' even if that column is present in
the table.
But, if I drop all publications (pub1 to pub5), then the whole thing works
perfectly fine. But it is not feasible to drop ALL publications (even the
ones not related to this change) to change the filter clause of 1 article for
just 1 publication. Is there any way out other than dropping the publications?
Thanks in advance for help.
Regards,
Shweta
exactly how are you deploying your publication to your SQL CE clients?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Shweta" <Shweta@.discussions.microsoft.com> wrote in message
news:697E3FFF-8A77-4FC1-ABCE-747679F84DF3@.microsoft.com...
> Hello,
> I've merge replication set between SQL Server 2000 & SQL CE.
> Whenever I try to add filter clause to the existing publication, it gives
> error mentioning the column name used in the filter clause.
> Ex. Let's say I've 5 publications - Pub1, Pub2, Pub3, Pub4, Pub5.
> If I add filter clause say 'Employee_Status <> 0' then it throws the error
> as 'Invalid Column Name 'Employee_Status'' even if that column is present
in
> the table.
> But, if I drop all publications (pub1 to pub5), then the whole thing works
> perfectly fine. But it is not feasible to drop ALL publications (even the
> ones not related to this change) to change the filter clause of 1 article
for
> just 1 publication. Is there any way out other than dropping the
publications?
> Thanks in advance for help.
> Regards,
> Shweta