怎样手工删除数据库里的Merge Replication信息

王朝other·作者佚名  2006-01-09
宽屏版  字体: |||超大  

1. The best way is to run sp_removedbreplication.

2. After you run sp_removedbreplication, you may run the following

script in your restored database. This script will generate the drop

commands for replication related system tables, views, stored procedures

and triggers. You may check the generated output first to make sure it

does not drop your own user object, and then run the output to drop

these information.

set nocount on

Select 'drop table ' + name from sysobjects

where name like '%conflict%' and type='u'

Select 'drop table ' + name from sysobjects

where name like 'MSMerge%' and type='u'

Select 'drop trigger ' + name from sysobjects

where type = 'tr' and status < 0 and category = 2

Select 'drop proc ' + name from sysobjects

where name like 'sp_%' and type ='p' and category = 2

Select 'drop proc ' + name from sysobjects

where name like 'sel_%' and type ='p' and category = 2

Select 'drop view ' + name from sysobjects

where name like 'tsvw%' and type ='v' and category = 2

Select 'drop view ' + name from sysobjects

where name like 'ctsv%' and type ='v' and category = 2

3. (optional step) you may use the steps in the following article to

make sure your user objects are no longer marked as being used in

replication (by change the replinfo column of the sysobjects to 0. This

steps is only needed if the replinfo column is not 0):

http://support.microsoft.com?id=326352

4. (optional step) check the steps in the following article to make sure

no columns are being marked as replicated:

http://support.microsoft.com?id=811899

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
© 2005- 王朝网络 版权所有