带有可用性组的SQL复制 [英] SQL replication with Availability groups

查看:71
本文介绍了带有可用性组的SQL复制的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


性能影响:



我们有一个SQL AG设置为几个数据库(主要和次要)


需要复制2个数据库。



是最好将辅助AG数据库复制到另一个独立的SQL实例,并在独立的SQL实例和辅助AG数据库之间进行复制设置



<请>,建议






解决方案

你好SQLrocket3003,



你不能这样做。在可用性组中,辅助数据库不能是发布者。您必须使用主数据库作为发布者。请参阅

复制,更改跟踪,&更改数据捕获 - Always On可用性组




如果要将两个数据库迁移到另一个实例,则最简单的方法是备份和还原。另一种选择可能是日志传送。但是,日志传送主数据库也必须位于可用性组的主副本中。


Performance implications:

We have a SQL AG Set up for a couple of databases (Primary and Secondary)

2 database requires to be replicated.

Is it a good idea to replicate between Secondary AG database to another standalone SQL instance with replication set-up between standalone SQL instance and Secondary AG database

please, advise



解决方案

Hi SQLrocket3003,

You cannot do it. In an availability group a secondary database cannot be a publisher. You will have to use the primary database as the publisher. Please refer to Replication, change tracking, & change data capture - Always On availability groups.

If you want to migrate the two databases to another instance, the easist way would be backup and restore. The other option could be log shipping. But the log shipping primary database also must reside on the primary replica of your availability group.


这篇关于带有可用性组的SQL复制的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆