July 9, 2004 at 9:18 pm
I have a db that is replicated and had conflict problems which have been rectified. Problem is I can not delete the previously system created conflict tables and stored procedures. They are all labeled dbo and unable to remove them. How can this be done? There are approximately 2000 of them. We had 190 tables and each time a conflict occured and was not cleared up prior to a snapshot created, a conflict table for each existing table along with several stored procedures seemed to be created.
July 11, 2004 at 5:40 pm
July 11, 2004 at 8:39 pm
Thanks for the suggestion. I had tried on a backup copy of the db (no replication) to do just that, and the system will not allow me to delete the tables and sp's due to "you tried to delete one or more system objects. They were not deleted". No other information or anything to help with it. Any way around that?
July 11, 2004 at 9:59 pm
You have to allow SYSTEM UPDATES to the System Tables. You enable this via the properties of the SQL Server. But I'm not sure that even that will allow you to DROP System Tables!
If it does allow you to DROP System Tables, BE CARFUL WHEN DOING THIS! I HAVE NOT EXPERIENCED YOUR SITUATION BEFORE, and I will not take responsibility if you happen to DROP necassary System Tables!
February 15, 2006 at 5:26 am
hi
how to allow system updates to the system tables?
November 19, 2006 at 7:25 pm
EXEC sp_configure 'allow',1
go
reconfigure with override
go
delete From sysobjects where name like 'conflict%'
EXEC sp_configure 'allow',0
go
reconfigure with override
go
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply