Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Replication / November 2006

Tip: Looking for answers? Try searching our database.

Reinitilaize without re-sending the data.

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jostein.solstad@gmail.com - 29 Nov 2006 10:04 GMT
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!
Paul Ibison - 29 Nov 2006 12:21 GMT
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 .
Hilary Cotter - 29 Nov 2006 13:44 GMT
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.

Signature

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

> Hi.
>
[quoted text clipped - 22 lines]
>
> Than you!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.