October 12, 2005 at 11:10 am
I have a database in production that is being replicated to a seperate instance of SQL Server2000. For development purposes, when I want the latest data from that database, I take a copy of the full backup and just restore it on my machine that doesn't have replication turned on.
When I try to make changes to specific tables on my development machine that are replicated in the production environment, I get errors saying that the table is replicated. There is even a "ghost" publisher and I can't delete that also because it says it can't find stored procedure .
Here is the error I receive when I try to drop a column:
ALTER TABLE DROP COLUMN failed because 'SellerOrderNumber' is currently replicated.
Does anyone know how I can clean up these replication artifacts on my development database so I can create scripts to modify the production database?
(I do know that when I modify the production db, I will have to delete the subscriptions, publishers etc. before I can modify the db. )
Thanks for your help.
David Petersen
David Petersen
dipetersen.com
October 17, 2005 at 8:00 am
This was removed by the editor as SPAM
October 18, 2005 at 10:33 am
Hi there,
Picked up this error before...
If you have more than one table doing this, it's going to a lot of work... I got the error on one table...
Setup this object to be replicated & then just remove it again...
That's it!!
October 18, 2005 at 4:48 pm
Try using sp_removedbreplication 'dbname'.
That should fix it.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply