Add Article on Merge Replication

Add Article on Merge Replication

Post by Marcelo Coll » Sat, 04 Jan 2003 00:34:16



    Can anyone help me with this?

        I have a merge replication with one publisher and one subscriptor
and this works fine, but I need to add one new article without resent all
snapshot database so the quention is how I can apply one article without
reaply all the first snapshot ?,
Thanks for all.

Marcelo Colla

 
 
 

Add Article on Merge Replication

Post by Hilary Cotte » Sat, 04 Jan 2003 02:25:31


the easiest way to do this would be to create a seperate
publication for this new article.
Quote:>-----Original Message-----

>    Can anyone help me with this?

>        I have a merge replication with one publisher and
one subscriptor
>and this works fine, but I need to add one new article
without resent all
>snapshot database so the quention is how I can apply one
article without
>reaply all the first snapshot ?,
>Thanks for all.

>Marcelo Colla

>.


 
 
 

Add Article on Merge Replication

Post by Michael McPhea » Sat, 04 Jan 2003 09:52:54


Even though replicatiopn requires you to generate the new snapshot, I think
you will find that only the schema and data changes will be merged at the
subscriber rather than the whole snapshot being applied.

-Mike


Quote:

>     Can anyone help me with this?

>         I have a merge replication with one publisher and one subscriptor
> and this works fine, but I need to add one new article without resent all
> snapshot database so the quention is how I can apply one article without
> reaply all the first snapshot ?,
> Thanks for all.

> Marcelo Colla

 
 
 

Add Article on Merge Replication

Post by Hilary Cotte » Sun, 05 Jan 2003 14:11:28


My understanding is that if you create a merge publication
and do a nosync with your subscribers merge replication
metadata and merge replication tables and triggers will
still be snapshotted to the subscriber.  If you do a sync
the data will also go to the subscriber.

>-----Original Message-----
>Even though replicatiopn requires you to generate the new
snapshot, I think
>you will find that only the schema and data changes will
be merged at the
>subscriber rather than the whole snapshot being applied.

>-Mike



>>     Can anyone help me with this?

>>         I have a merge replication with one publisher
and one subscriptor
>> and this works fine, but I need to add one new article
without resent all
>> snapshot database so the quention is how I can apply
one article without
>> reaply all the first snapshot ?,
>> Thanks for all.

>> Marcelo Colla

>.

 
 
 

Add Article on Merge Replication

Post by Michael Hote » Wed, 08 Jan 2003 07:08:14


You can add the article to the existing publication.  The wizard will tell
you that it is going to invalidate everything and resnapshot it.  Ignore
that message.  It will generate a snapshot for only the article you added in
and then transfer that to the subscriber.

--

Mike
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

 
 
 

1. Merge Replication with ftp fails after adding A New Merge Article

I have created a Merge replication between 2 SQL 2000 servers.  The one
server is configured to do a Pull (non anonymous) and the snapshot is being
downloaded over ftp.

If I add a table to the replication, I get a message indicating that I must
generate a new snapshot before changes from any subscriber can be merged.
It also indicated that only the snapshot of the new article will be used to
sync existing subscriptions.

I create the new snapshot, but when the server synchronized, I get an error
like this:

The schema script '\\<server name>\D$\Program Files\Microsoft SQL
Server\MSSQL\ReplData\ftp\<server name>_EM2_EM2 Proxy
Replication\20020125092210\A Test 9_257.sch' could not be propagated to the
subscriber.

It seems odd that it is trying to access it from the server share even
though this subscription is configured to use ftp.  Also note, that is not
even the location of the ftp configured in the publication.

I end up having to reinitialize the client, the synchronize to get the
changes.  This is not really acceptable over slow network links.

Is there any way to just get the snaphot of the new article to sync. as is
indicated when I make the change?

2. Date Type problems

3. problem while adding new article to merge replication

4. New to SQLXML

5. Merge replication adding articles

6. SQLEXEC Limitations in VFP 5.0???

7. Does Merge Replication transfer the rules, defaults, UDT's when bound to Article

8. ** FOR IMMEDIATE RELEASE - RECORD-BREAKING TPC-C RECORD!! **

9. Table Schema Change To Article In Merge Replication

10. Re-reading of Merge Replication articles during synchronisation

11. Merge Replication Filters - Article SubsetFilterClause vs separate MergeSubsetFilters

12. Maximum number of tables.Articles for Merge Replication

13. Merge Replication doesn't sync all articles