SQL Server 相当于 MySQL 多主复制？
MSSQL 是否有相当于 MySQL 的多主复制？如果是，它在 SQL Express 2008 中可用吗？我还看到它被称为两节点循环复制。
基本上，我有一个办公室内数据库，我希望它与云数据库完美（相对:)）同步（我们将通过 VPN 访问）。读取和写入发生在两个节点上。
Is there an MSSQL equivalent of MySQL's multi-master replication? If so, is it available in SQL Express 2008? I've also seen it referred to as two node circular replication.
Basically, I have an in-office database that I want to be perfectly (relatively :) )in sync with a cloud database (we will have access via VPN). Reads and writes occur at both nodes.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
SQL Server 2008 企业版和标准版提供：
SQL Server 2008 Express 有限制 功能：
在这两种情况下，您都需要编写定制的解决方案。
SQL Server MVP Deep Dives 中有一个很棒的章节，名为“穷人的 SQL Server 日志传送”。 ”它将带您完成整个过程。
SQL Server 2008 Enterprise and Standard editions offer:
SQL Server 2008 Express has limited functionality with:
In both cases, you'll need to write a customized solution.
There is an excellent chapter in SQL Server MVP Deep Dives called "The Poor Man's SQL Server Log Shipping." It will take you through the entire process.
当您说云数据库时，您指的是 SQL Azure 吗？如果是这样，SQL Azure 不支持复制。
如果您的云数据库是 SQL Server 的完整副本（即不是 Express），您可以设置具有可更新订阅的事务发布，或使用合并发布。这两个选项都允许您同步任一数据库中的更改。
编辑
澄清一下，您可以使用 SQL Server Express 进行复制，但只能作为订阅者使用。发布者需要是Workgroup版本或以上版本。
When you say a cloud database, do you mean SQL Azure? If so, SQL Azure doesn’t support replication.
If your cloud database is a full copy of SQL Server (i.e. not Express) you can set up a transactional publication with updatable subscriptions, or use a merge publication. Both options will let you synchronise changes in either database.
Edit
Just to clarify, you can use SQL Server Express for replication, but only as a subscriber. The publisher needs to be Workgroup edition or above.
除了其他人发布的内容之外，我还想提到合并复制，以及 MSDN 上有关 选择适当的复制类型。基本上，您选择合并还是事务（更新订阅者）取决于不同节点的写入比例以及冲突更改的可能性。
In addition to what others have posted, I'd also mention merge replication, and an article on MSDN about Selecting the Appropriate Type of Replication. Basically, whether you choose Merge or Transactional (with updating subscribers) depends on what the proportion of writes are at the different nodes, and the likelihood of conflicting changes.
点对点事务复制。是企业独有的功能。另一种选择是事务复制的可更新订阅，请参阅事务复制的可更新订阅。最后，您可以使用 Service Broker< /a>，这是唯一适用于 Express 客户端的选项，只要“云”版本是非 Express 即可。
Peer-to-Peer Transactional Replication. Is an Enterprise only feature. Another option is an updatable subscription for Transactional Replication, see Updatable Subscriptions for Transactional Replication. And finally you can roll your own using Service Broker, which is the only option which will work with an Express client, as long as the 'cloud' edition is non-Express.