Re: reinstall of the subscriber server

You don't need to shut down the log reader to delete the subscription
database, rather you need to shut down the distribution agent. The log
reader is connected to the publication database and the distribution
database. I am unfamiliar with the rplcmds command.

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

"Wingman" <Wingman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1F21FF5C-083A-43CB-9EA6-59EC9A103AA2@xxxxxxxxxxxxxxxx
> Thanks.
>
> One quick follow-up question. I understand the idea of the purpose of the
> log reader agent and I don't need to shut it down for what I am planning
> to
> do. I noticed that if I want to delete a subscriber database, I need to
> shut
> the log reader agent down because the log reader agent is running a
> command
> "rplcmds' and is connected to the subscriber database. First of all, is
> my
> finding correct? Secondly, can you explain what this command does?
>
> wingman
>
> "Hilary Cotter" wrote:
>
>> As long as the server name, database name, and IP address are identical
>> this
>> will work.
>>
>> --
>> 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
>>
>> "Wingman" <Wingman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:9E5E069D-1FBD-4A37-8DA3-C09BCCE53F8E@xxxxxxxxxxxxxxxx
>> > We are using SQL 2K std with s4 and are using Push subscription method.
>> >
>> > We need to upgrade some hardware in the subscriber server which will
>> > require
>> > us to do a total reinstall of the OS and SQL server software. Since we
>> > are
>> > using push subscription, most of the replication settings are on the
>> > publishing server. When we do the server upgrade, I will stop the
>> > distribution agent so it won't do any transfer until the server is up.
>> > I
>> > like to know if I back up the subscriber database and restore it on the
>> > same
>> > upgraded server. Will the replication work like as usual? Are there
>> > any
>> > steps I need to consider?
>> >
>> > wingman
>>
>>
>>


.

Relevant Pages

  • Re: SQL2000 - Merge Replication - Timeout error
    ... The timeout is in your publisher and distributor server, ... Then, update the database statistics. ... Run profiler on the subscriber to see what is going on? ...
    (microsoft.public.sqlserver.replication)
  • Re: transactional replication problem
    ... If the distribution agen can't connect to the subscriber, ... Looking for a SQL Server replication book? ... > server B. Problem is with only one database. ...
    (microsoft.public.sqlserver.replication)
  • Transation replication with updateable subscribers
    ... I have a main database that I need to distribute a copy of to another server ... The Subscriber will be a SQL server 2000 std edition ... was supposed to create a publication that was a transactional publication ...
    (microsoft.public.sqlserver.replication)
  • Re: Subscriber Transaction Logs Too Large
    ... I would advise you to put the subscriber database into bulk ... in full recovery model and dump the log every 15 minutes or so. ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Transactional replication. Error 18752 on log reader agent
    ... only "strange" thing is that it has 2 publications in the same database. ... Log reader agent parameters after tunning it a couple of times: ... In SERVER A the transaction log file size of one database which is being ... Error del agente con un estado 'Reintento'. ...
    (microsoft.public.sqlserver.replication)
Loading