SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2012 Forums
 SQL Server Administration (2012)
 distribution db corruption
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

kalyani.esl
Starting Member

5 Posts

Posted - 08/26/2013 :  15:32:54  Show Profile  Reply with Quote
Distribution is on separate server C of sqlserver 2012.
I have transactional replication of publisher on Server A and
distributor on Server B.
If distribution crashes on Server C and i restore the distribution database with latest available backup will replication resume back.

Bustaz Kool
Flowing Fount of Yak Knowledge

USA
1643 Posts

Posted - 08/27/2013 :  19:15:10  Show Profile  Reply with Quote
Originally, I thought that this would be a straight forward answer to a straight forward question. The Distributor is tasked with insuring that each Subscriber gets the data changes. It does not commit the change until each Subscriber acknowledges receipt of the change. Simple. Then I re-read your question and I became perplexed. If the Distributor is on B how could it crash on C? If the C server crashed, how could restoring anything on B fix C? I'm not sure if I understand your situation but if I do... Server A will continue to make changes and report them to the Distributor on B. The Distributor on B will continue to TRY to talk to the Subscriber on C. Since C has crashed, it won't be able to. If a sufficient amount of time elapses, the Distributor will give up and declare that a new snapshot is required. The actual timeout value is a configurable aspect of your publication. If server C can be brought back within time, the Distibutor will complete the data change and carry on as normal. If you restore the Subscriber database on C within the timeout window, I'm not sure whether the Distributor will recognize that the databases are out of sync but I suspect that it will and demand a new snapshot. (I could be wrong about that)

HTH

PS, If I don't really understand your situation, please feel free to ignore this completely.

=================================================
The cure for anything is salt water -- sweat, tears, or the sea. -Isak Dinesen
Go to Top of Page

kalyani.esl
Starting Member

5 Posts

Posted - 08/28/2013 :  15:17:58  Show Profile  Reply with Quote
I am sorry it was a typo.
Distribution is on separate server C of sqlserver 2012.
I have transactional replication of publisher on Server A and
subscriber on Server B.
If distribution crashes on Server C and i restore the distribution database with latest available backup will replication resume back.
Go to Top of Page

Bustaz Kool
Flowing Fount of Yak Knowledge

USA
1643 Posts

Posted - 08/29/2013 :  19:08:58  Show Profile  Reply with Quote
"That's an excellent question!" which is my way of saying that I have no idea. I would, however, be very interested in finding out the results of your restore. Take a look at the "sync with backup" setting in BOL to see if this might be an answer to your issue.

=================================================
The cure for anything is salt water -- sweat, tears, or the sea. -Isak Dinesen
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.05 seconds. Powered By: Snitz Forums 2000