How to reinitialize a table in transactional publication. -- sql server replication

sql server replication : How to reinitialize a table in transactional publication.

Nags
4/13/2004 2:53:14 PM

I have set-up replication using transactional publication and I have
configured subscription to be near continuous.

I have this issue. When setting up subscription I have specified that the
subscription database already had data. So when the snapshot agent is
initialized it does not recreate the tables on the subscription database.
This is ok. But, now if I was to re-initialize only one of the tables, how
do I achieve this without breaking replication.

-Nags

Hilary Cotter
4/13/2004 10:31:48 PM

You can't really do this.

If you start with a no-sync, you can't re-initialize. Only subscriptions
that were set for automatic synchronization can be re-initialized.

What I do in situations like this is to drop the article, and then recreate
it in a new publication.

[quoted text, click to view]

Nags
4/14/2004 7:22:20 AM

Can we drop an article once the tables are published and also subscribed ?
I thought that once there is a subscription on a publication (at least in
transactional publication) we cannot drop the article.

-Nags

[quoted text, click to view]

Hilary Cotter
4/14/2004 1:24:52 PM

You will have to drop the subscription for both automatic and nosync
subscriptions, then you can drop the article.

[quoted text, click to view]

Nags
4/14/2004 2:51:18 PM

But, I do not want to break replication :(

-Nags
[quoted text, click to view]

Olivier
4/16/2004 11:27:31 PM

[quoted text, click to view]

You are not very well..
However, there are several tricks you can try:
a) you can afford having no transaction on the source table for a
certain time
=> put a trigger for insert / update / delete on the table which
always raise error and rollback
=> wait the log reader agent and the distribution agent have purged
any pending transaction on this table
=> bulk copy your table from publisher to subscriber
=> remove the trigger

b) you can also create a new publication on the table ( I never tried to
publish twice a table on the same database, but you can always create a
"mirror" table on the publishing database that you keep in sync with
triggers )

On the subscriber, subscribe to this new publication and wait for
synchronisation

Now, here is the trick:
On the publisher you have articles A and A2 which you know are in sync
On the subscriber you have tables Arep and A2rep and you know that A2rep
is in sync

So, stop the log reader agent.
Wait long enough so that the distributing agents tell "no more transactions"

Copy A2rep into Arep

restart log reader agent.

Now Arep is sync'ed and you can drop all the A2 stuff.

If you are not familiar with these operations, you might make a
rehearsal on a test server before trying your production server!

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server replication

View Other Months
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007

home · blog · groups

Questions? Comments? Contact the dn