all groups > sql server replication > november 2006 >
You're in the

sql server replication

group:

Reinitilaize without re-sending the data.


Re: Reinitilaize without re-sending the data. Paul Ibison
11/29/2006 12:00:00 AM
sql server replication: The simplest solution is to drop the subscription, use DataCompare or
TABLEDIFF to sync up the tables then do a nosync initialization.
Generally the log-reader is set to run continuously. There are 2 main
reasons I can think why this is so - lower latency and minimise the size of
the transaction log (the log can't be truncated until it's been read by the
logreader).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Re: Reinitilaize without re-sending the data. Hilary Cotter
11/29/2006 12:00:00 AM
Do a no-sync subscription. Then run a validation to determine which tables
are out of sync. Then it is a matter of getting these back in
synchronization. You can use tablediff or RedGates data compare for this.

--
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



[quoted text, click to view]

Reinitilaize without re-sending the data. jostein.solstad NO[at]SPAM gmail.com
11/29/2006 2:04:08 AM
Hi.

I have a subsription that needs to be reinitialized because it has been
marked as inactive. Instead of reinitializing and then have to transfer
a new snapshot, that would caus all sorts of key violations, i would
like to do the following.

1.Drop the subscription.
2.Add subscription with option that the subscribers has the schema and
data.
3.Copy the pending transactions

The problem is, when you drop the subscription, the pending
transactions are truncated, so the question is.

How can i copy all the commands from the distribution agent, that is
supposed to go to a specific subscriber, so that i can just connect to
the subscriber and run them manually after i have set up the new
subscription?

Also have a second question.
We don't have a lot of changes, and it seems like having the log reader
running contuniously is not neccessary. Can i just change the log
reader job to run on a reccuring schedule with Enterprise Manager?

Than you!
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 in the sql server replication group.
AddThis Social Bookmark Button
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