Re: Orphaned Publication
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Fri, 15 Jun 2007 10:58:50 -0400
you have to reverse engineer the stored procedures to see which
publisher/publication/subscriber/subscription is bogus and then delete it.
Bogus entries in distribution.dbo.syspublications are the most frequent
culprit.
Use sp_droppublication to try to remove it.
--
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
"Matt" <Matt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3A2B6714-693E-4CE8-BEB7-B611992DC09B@xxxxxxxxxxxxxxxx
A database has been deleted that had publications set up and these are now
causing errors in the 'Replication Monitor'.
Under Replication Monitor - Publishers - SeverName - dbname we have a
failed
snapshot agent that says [SQL-DMO]The name 'dbname' was not found in the
Databases collection. If the name is a qualified name, use [] to separate
various parts of the name, and try again.".
Under Replication Monitor - Agents - Snapshot Agents and this has the same
error.
If I try and delete the entry under Under Replication Monitor -
Publishers -
SeverName - dbname I receive the following error:
"[SQL-DMO]The name 'dbname' was not found in the Databases collection. If
the name is a qualified name, use [] to separate various parts of the
name,
and try again."
Under Replication - Publishers there are no entries.
How can I tidy this up and remove the entries and thus the big red cross?
Thanks in advance.
.
- Prev by Date: Re: Similar to "Simplest way to move an entrie database"
- Next by Date: Re: Workarround in identities in Merge Replication to avoid the use of auto identity range
- Previous by thread: Merge replication performance dropping. Opinions?
- Next by thread: Re: Delete subscriptions
- Index(es):
Relevant Pages
|
