这会强制合并复制拓扑重新初始化吗？

发布于 2024-08-25 21:09:47 字数 522 浏览 5 评论 0原文

我需要向作为复制集一部分的表添加几列。它不是约束列，也不是任何文章过滤器的一部分，并且允许 NULL。我有一个很好的想法，我可以运行这个：

ALTER TABLE tblPlanDomain 
    ADD ReportWageES VARCHAR (100) NULL

而不是强迫我的所有客户重新初始化，但我希望得到一些保证。任何人都可以为我验证这一方式或另一方式吗？

谢谢，

编辑：

这就是我所说的 --> http://msdn.microsoft.com/en-us/library/ms151870。 aspx

基于此，我的问题的答案似乎是否，但我仍然希望得到人工确认。

原文

I need to add a couple of columns to a table that is a part of a replication set. It is not a constraint column or a part of any article filters and it allows NULL. I have a pretty good idea that I can run this:

ALTER TABLE tblPlanDomain 
    ADD ReportWageES VARCHAR (100) NULL

and NOT force all my clients to reinitialize but I was hoping for some reassurance. Can anyone verify this one way or the other for me?

Thanks,

EDIT:

This is what I am talking about --> http://msdn.microsoft.com/en-us/library/ms151870.aspx

It would seem, based on that, that the answer to my question is NO but I would still like a human confirmation.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

木槿暧夏七纪年 2024-09-01 21:09:47

我可以确认您可以在合并复制中添加所需数量的列，而无需重新初始化整个复制。诸如

ALTER TABLE myTable ADD myColumn myDataType Null

“不会强制重新初始化”

之类的指令，诸如添加索引或外键约束之类的指令也可以轻松传播给订阅者，而无需重新初始化。

向合并拓扑添加新表也可以轻松完成：虽然需要重建快照，但合并过程不会从头开始：仅，并且仅将新表的结构和数据发送给订阅者复制后。这就是说，请小心不要复制依赖于其他非复制表实现约束的表......

I can confirm that you are able to add as many columns as needed in a merge replication without reinitializing the whole replication. Instructions such as

ALTER TABLE myTable ADD myColumn myDataType Null

Will not force a reinitialisation

Instructions such as adding indexes or foreign key constraints can also be easily propogated to subscribers without reinitialisation.

Adding a new table to a merge topology can also be done easily: though it requires the rebuilding of the snapshot, the merge process will not restart from scratch: only , and only the new table's structure and data will be sent to the subscribers on the following replication. This said, be carefull not to replicate tables that implement constraints depending on other non replicated tables ...

回复收藏 0 原文

~没有更多了~