prakashcn@hotmail.com wrote:
> Hey
>
> If u hav droped the publication already dont wory forget it
> and continue.
>
> The other way is in the publication DB u hav some tables
> which keep tracks of the subcription info just clear that
> rows also. or just drop the subscription DB also
>
> And other thing what u hav done is u hav droped the DB
> If the DB is droped then automatically publication is deleted
> and related information tables are also deleted which holds
> the subscription information
>
> I really dont know what is stoping u to continue to restore DB
> from the backup and dont get panic and start the
> restore process
>
> -Cheers - Prax
>
>
> Q. John Chen wrote:
> > Here was my problem.
> >
> > I have a database with replication. All I need to do was restore the
> > database from a backup (totally different data from another server).
> > The restore process was messed up because I was not aware there is
> > replication in place. So the database status is always loading. I have
> > to use sp_removedb and then restore the db.
> >
> > But the publication is still there (with a push subscription). Can not
> > do anything with Enterprise manager either. So I did a
> > sp_dropReplication but I later noticed that I have to do
> > sp_dropsubscription first.
> >
> > Now I am stuck:
> >
> > I can not drop the subscription (complaining error 20026 can not find
> > publication)
> > and I can not create publication either (compaling there is already a
> > subscriptin)
> >
> > Anyone just tell how to get rid of this and I can start over.
> >
> > Thanks
> >
> > John