Re: Log Reader Agent remains after removing replication

Tech-Archive recommends: Fix windows errors by optimizing your registry

Can you do this query for me?

select originating_server,name,server, command from msdb.dbo.sysjobs join
msdb.dbo.sysjobsteps on
msdb.dbo.sysjobsteps.job_id=sysjobs.job_id and subsystem='logreader'

--
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:FD764EC8-F84C-4CDD-9811-E98215385E3D@xxxxxxxxxxxxxxxx
What I have done is removing replication and then renaming the original
database to a new name and setup replication for the renamed database. The
original Log Reader and Distribution agents still remain and show error
sign
even after I removed the jobs and restarted the server. The error now says
it
could not access the database because it does not exist. Is there a way to
remove these unwanted agents?

"Hilary Cotter" wrote:

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.








.

Relevant Pages

  • Re: Searching with AND - the Google way
    ... Hilary Cotter ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Log Reader Agent remains after removing replication
    ... Looking for a SQL Server replication book? ... "Hilary Cotter" wrote: ... database to a new name and setup replication for the renamed database. ... original Log Reader and Distribution agents still remain and show error ...
    (microsoft.public.sqlserver.replication)
  • Re: create store procedure to incremental populate full text index
    ... > How to create store procedure to perform full population of full text ... >> Hilary Cotter ... >> Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Keywords Meta Data search
    ... Hilary Cotter ... >> Looking for a SQL Server replication book? ... >> Now available for purchase at: ...
    (microsoft.public.inetserver.indexserver)
  • Re: sql 2005 merge replication direction
    ... Looking for a SQL Server replication book? ... "Hilary Cotter" wrote: ... Director of Text Mining and Database Strategy ...
    (microsoft.public.sqlserver.replication)