I have disabled publisher, distributor and subscriber; no publications exist
on publisher. However, when I try to alter a table on former publisher I get
this error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
table 'dbo.MAIN' because it is being used for replication.
Please help, thank you in advance for your time!
Leon ShargorodskyRun stored proc sp_removedbreplication and see if that fixes your problem.
Mike
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> I have disabled publisher, distributor and subscriber; no publications
exist
> on publisher. However, when I try to alter a table on former publisher I
get
> this error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
> table 'dbo.MAIN' because it is being used for replication.
> Please help, thank you in advance for your time!
> Leon Shargorodsky|||No, I'm still getting the same error: "table is being used for replication"
"Mike Wengler" wrote:
> Run stored proc sp_removedbreplication and see if that fixes your problem.
> Mike
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> > I have disabled publisher, distributor and subscriber; no publications
> exist
> > on publisher. However, when I try to alter a table on former publisher I
> get
> > this error:
> >
> > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
> > table 'dbo.MAIN' because it is being used for replication.
> >
> > Please help, thank you in advance for your time!
> >
> > Leon Shargorodsky
>
>|||NOT RECOMMENDED Under normal circumstances only after trying ALL other
solutions . . but I have had this problem resolved in the past by reseting
the value in replinfo column in sysobjects to 0.
HTH
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> No, I'm still getting the same error: "table is being used for
replication"
> "Mike Wengler" wrote:
> > Run stored proc sp_removedbreplication and see if that fixes your
problem.
> >
> > Mike
> >
> > "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote
in
> > message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> > > I have disabled publisher, distributor and subscriber; no publications
> > exist
> > > on publisher. However, when I try to alter a table on former publisher
I
> > get
> > > this error:
> > >
> > > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop
the
> > > table 'dbo.MAIN' because it is being used for replication.
> > >
> > > Please help, thank you in advance for your time!
> > >
> > > Leon Shargorodsky
> >
> >
> >|||THANK YOU SO MUCH! It worked!!!
"Olu Adedeji" wrote:
> NOT RECOMMENDED Under normal circumstances only after trying ALL other
> solutions . . but I have had this problem resolved in the past by reseting
> the value in replinfo column in sysobjects to 0.
> HTH
>
>
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> > No, I'm still getting the same error: "table is being used for
> replication"
> >
> > "Mike Wengler" wrote:
> >
> > > Run stored proc sp_removedbreplication and see if that fixes your
> problem.
> > >
> > > Mike
> > >
> > > "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote
> in
> > > message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> > > > I have disabled publisher, distributor and subscriber; no publications
> > > exist
> > > > on publisher. However, when I try to alter a table on former publisher
> I
> > > get
> > > > this error:
> > > >
> > > > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop
> the
> > > > table 'dbo.MAIN' because it is being used for replication.
> > > >
> > > > Please help, thank you in advance for your time!
> > > >
> > > > Leon Shargorodsky
> > >
> > >
> > >
>
>
Showing posts with label exist. Show all posts
Showing posts with label exist. Show all posts
Friday, March 23, 2012
Saturday, February 25, 2012
Replication Issue with ERROR 20026 publication '%s' does not exist
We have replication between two Microsoft SQL2000 servers. We took
down replication (had no problem) then backed up the database (no
problem). Tried to make some changes but had to delete the publication
first and then we ran into some other issuse (not a big problem). So
we decided to restore the database from the backup. the issue came
about because the publication has been deleted but the restored
database still has it listed. Bacause of this we cannot make any
changes to the database, further more if we try to delete the
publication it wont let us because it doesnt exist. So we are kind
caught in a bind (This is the main issue).
can you drop the publications using sp_droppublication?
Follow these instructions - http://support.microsoft.com/kb/324401
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
<ebade2000@.gmail.com> wrote in message
news:1174060376.222600.269530@.p15g2000hsd.googlegr oups.com...
> We have replication between two Microsoft SQL2000 servers. We took
> down replication (had no problem) then backed up the database (no
> problem). Tried to make some changes but had to delete the publication
> first and then we ran into some other issuse (not a big problem). So
> we decided to restore the database from the backup. the issue came
> about because the publication has been deleted but the restored
> database still has it listed. Bacause of this we cannot make any
> changes to the database, further more if we try to delete the
> publication it wont let us because it doesnt exist. So we are kind
> caught in a bind (This is the main issue).
>
|||Fixed it yeeeha. Thanks for your help Hilary what ended up working for
me was "sp_removedbreplication". The other stored procedures will work
if the publication pr replication existed (which was not my case)
down replication (had no problem) then backed up the database (no
problem). Tried to make some changes but had to delete the publication
first and then we ran into some other issuse (not a big problem). So
we decided to restore the database from the backup. the issue came
about because the publication has been deleted but the restored
database still has it listed. Bacause of this we cannot make any
changes to the database, further more if we try to delete the
publication it wont let us because it doesnt exist. So we are kind
caught in a bind (This is the main issue).
can you drop the publications using sp_droppublication?
Follow these instructions - http://support.microsoft.com/kb/324401
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
<ebade2000@.gmail.com> wrote in message
news:1174060376.222600.269530@.p15g2000hsd.googlegr oups.com...
> We have replication between two Microsoft SQL2000 servers. We took
> down replication (had no problem) then backed up the database (no
> problem). Tried to make some changes but had to delete the publication
> first and then we ran into some other issuse (not a big problem). So
> we decided to restore the database from the backup. the issue came
> about because the publication has been deleted but the restored
> database still has it listed. Bacause of this we cannot make any
> changes to the database, further more if we try to delete the
> publication it wont let us because it doesnt exist. So we are kind
> caught in a bind (This is the main issue).
>
|||Fixed it yeeeha. Thanks for your help Hilary what ended up working for
me was "sp_removedbreplication". The other stored procedures will work
if the publication pr replication existed (which was not my case)
Subscribe to:
Posts (Atom)