Thanks for the reference.
In your book there is mention of a second volume for merge replication. Is
"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:uy11nLFcFHA.720@TK2MSFTNGP15.phx.gbl...
> Nope. Basically you need to cluster your distributor and hope for the
> best.
>
> There is a kb article which describes how to recover from this.
>
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;886839 >
> I am working on an article of my own explaining how to do 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 > "Bob Castleman" <nomail@here> wrote in message
> news:uzw0o4EcFHA.3204@TK2MSFTNGP12.phx.gbl...
>> So what happens when the Distribution Server blows a gasket? Somehow I
>> get
>> the feeling that restoring from last nights backup isn't going to get
> things
>> back to normal? I ask because we are going to build a replication
>> solution
>> that will fall under Sarbanes Oxely issues, one of which is documented
>> business continuity plans. Our solution will likely have a dedicated
>> distribution server and even though we haven't even budgeted hardware
>> yet,
> I
>> am having visions of a major meltdown and a trip to the mental ward.
>>
>> P.S. to Hilary Cotter. I think your replication book is great. I would
>> suggest that a follow up title would be a book (or additional chapters in
> a
>> new edition) that deal with such questions as replication headaches
>> during
>> recovery and restoration. At least from personal experience, our worst
> days
>> as IT people are when we are under the gun to restore failed services.
>>
>>
>> Bob Castleman
>> DBA Poseur
>>
>>
>
>