Replication on Backup

Hey all...here s my problem, let s see if u can help me please ! :
I have a DB with some tables published in X server, i made a backup of that
database, and restore that backup on another server ( Y ) , but it s still
beeing locked for the replication service, but the Y server doesnt have that
service active... so.. when i want to alter a table, i had the "YOU CANT
DROP THE TABLE BECAUSE IT S BEEING USING FOR REPLICATION.. " ( or something
like that ) .. how can i drop all suscriptions and publications services
from that database ?
tnx!
Try sp_removedbreplication.
If this doesn't remove everything you want, there is a stored procedure to
do this called sp_MSunmarkreplinfo which takes a tablename as a parameter.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanx Paul !! .. so, after that, i have to delete rowID fields and i have
the original DB right?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uU6$xoqGFHA.1392@.TK2MSFTNGP10.phx.gbl...
> Try sp_removedbreplication.
> If this doesn't remove everything you want, there is a stored procedure to
> do this called sp_MSunmarkreplinfo which takes a tablename as a parameter.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Is that a Enterprise Manager's BUG ?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uU6$xoqGFHA.1392@.TK2MSFTNGP10.phx.gbl...
> Try sp_removedbreplication.
> If this doesn't remove everything you want, there is a stored procedure to
> do this called sp_MSunmarkreplinfo which takes a tablename as a parameter.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Do you mean the RowGuids? They'll only be there if you're using some sort of
updating subscriber or merge replication. They'll need removing manually,
alson with any associated check constraints if you have automatic range
management set up.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I don't know if I'd call it a bug as such, just a little messy perhaps.
Several things may be left behind - check constraints, rowguids, conflict
tables etc. In some cases there may be user code that depends on these
objects eg the extra replication guid columns, in which case always
automatically removing them would be a disaster. Anyway, there are some
procedures knocking around which'll remove these extra bits (Hilary has
posted up a version on tis newsgroup a few times). Also, you'll like SQL
Server 2005 - there is the option to do a 'hard' version of
sp_removedbreplication which automatically removes all this replication
objects.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)