破坏 SQL Server 复制
我有一个新客户，等等，我需要中断从他们的家庭办公室到另一个数据库的 SQL Server 2000 复制，他们将完全删除该数据库（在某些托管位置，不再需要它）。
我相信，总部的那个人就是“出版商”。 老实说，我认为我们可以删除另一个数据库，而家庭办公室的数据库可以正常运行，但最好稍微清理一下它并摆脱出版物/订阅的东西。
我关心的一个问题是身份插入。 在具有自动分配的整数主键的表上，每个数据库都会“保留”它将使用的 id 块，这样它们在同步时就不会互相干扰。
那么，如果我只是转储复制内容，数据库会愉快地插入直到达到其自动编号范围的上限吗？ 然后会发生什么？
I've got a new client, blah blah blah, I need to break SQL Server 2000 replication from their home office to another database that they are going to completely drop (at some hosting place, it is no longer needed).
The one at the home office is the "Publisher", I believe. Honestly, I think we could just delete the other database and the home office one would run fine, but it would be nice to clean it up a bit and get rid of the publications/subscriptions stuff.
The one issues I'm concerned about is the identity insert. On tables with an auto-assigned integer primary key, each database would "reserve" a block of ids that it would use so they wouldn't trample on each other when synching up.
So, if I just dump the replication stuff, will the database insert happily until it hits the upper bound of its auto-number range? What happens then?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在开始实施任何更改之前，您需要清楚地确定每个数据库和服务器在复制拓扑中所扮演的角色。
作为进一步的预防措施，我还建议您编写复制配置的脚本，以便您可以安全地保存它的参考。
有关如何正确删除特定复制角色（即订阅者/发布者/分发者）的详细信息。
请参阅联机丛书：删除复制
You need to clearly identify the roles that each Database and Server are playing in your replication topology before you start rolling out any changes.
As a further precaution, I would also suggest that you script out your Replication Configuration, so that you have a reference of it for safe keeping.
For details on how to correctly remove a specific replication role i.e. Subscriber / publisher / Distributor.
See Books Online: Removing Replication