{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Juvenile、少年° 的问题《Multiple SQL replication types》','https://www.manongdao.com/q-983278.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
We currently have two SQL databases that are utilizing a merge replication. We would like to setup a separate transactional replication off one of the databases to a third database. Is this possible? If so, do we need to change anything with our distributor?
Thanks!
Yes this is possible. Nothing needs to change with the Distributor.
However, if you ever have a Merge node receive data from a Transactional Replication topology then you will need to make sure the property @published_in_tran_pub for your Merge articles is set to true to ensure the Merge triggers fire properly. It sounds like this won't apply in your case unless the third database is a Merge publisher/subscriber.