Re: Log Reader Agent remains after removing replication
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Fri, 10 Feb 2006 23:32:53 -0500
Refresh the folder to see if it stays there. Also issue a
sp_MSload_replication_status
--
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
"mpWong" <mpWong@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:14197959-4FDF-4B8B-86BA-F45FD7868A9A@xxxxxxxxxxxxxxxx
Even after removing related jobs and restarted the server, the Log Reader
and
Distribution agents still display in the folder showing error sign. Is
there
a way to remove them from the folder in Enterprise Manager?
"Hilary Cotter" wrote:
You can delete the job from the management folder.
--
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
"mpWong" <mpWong@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FECBE549-7DE1-4FFA-B464-13DD72B63BFE@xxxxxxxxxxxxxxxx
After I execute sp_removedbreplication for a database on SQL Server
2000
SP3,
the Log Reader Agent remains and shows error "could not execute
sp_replcmds".
How to remove this particular agent? There is replication going on for
a
few
other databases.
.
- References:
- Re: Log Reader Agent remains after removing replication
- From: Hilary Cotter
- Re: Log Reader Agent remains after removing replication
- Prev by Date: Re: 10 times more commands than transactions since adding fields
- Next by Date: Re: non logged transactions with transactional replication
- Previous by thread: Re: Log Reader Agent remains after removing replication
- Next by thread: Re: Log Reader Agent remains after removing replication
- Index(es):
Relevant Pages
|