January 21, 2008 at 8:07 am
We recently did a restore of SQL 2000 onto our server. Everything proceeded fine with the restore process. I restored the master database and then proceeded to restore all additional databases.
But now we are having problems with replication. The system bellieves it is setup for replication...but i have not made the server a distributor nor a publisher (it was prior to restore). It has all the databases we were replicating...but now i cannot delete them. I recieve the following errors.
Invalid column name 'min_distretention'
invalid column name 'max_distretention'
invalid column name 'history_retention'
Can anyone give me some ideas on how to proceed. I have considered restoring the msdb from a clean install....but i am looking for the best alternative.
January 21, 2008 at 8:58 am
I'm not really sure to understand your problem but I'd try some suggestions.
You can remove Replication for the whole server from the Enterprise Manager >> Tools
You can have a look to the KB article
How to manually remove a replication in SQL Server 2000 or in SQL Server 2005
http://support.microsoft.com/kb/324401/en-us
This code may work for remove publication for a single database
sp_replicationdboption 'database_name','publish', 'false'
go
sp_replicationdboption 'database_name','merge publish', 'false'
go
drop database database_name
go
You said that you restore SQL Server master database, do you really to do that? Could not you do a clean install of SQL Server and attach databases?
Regards Ramon
Regards Ramon
January 21, 2008 at 9:46 am
when i try to use the enterprise manager to remove the replication...i receive the errors stated. it will not allow me to delete them.
when we restored the sql from tape backups...i did not restore the msdb database..i think this is what hosed up the system.
The server 'thinks' its replicating (databases listed under replication)...but nothing is actually occuring....
January 21, 2008 at 9:54 am
As far as I Know, replication settings and configuration are stored on distribution database and on every published database.
Which databases did you restore?
I don't know your replication topology, security context or how many databases must you take back, but, couldn't you make a clean install of SQL Server and configure replication?
Regards Ramon
Regards Ramon
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply