{"version":"1.0","provider_name":"dbi Blog","provider_url":"https:\/\/www.dbi-services.com\/blog","title":"SQL Server 2016 AlwaysOn: distributed availability groups","type":"rich","width":600,"height":338,"html":"<blockquote class=\"wp-embedded-content\" data-secret=\"PHdrWDcNVd\"><a href=\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-distributed-availability-groups\/\">SQL Server 2016 AlwaysOn: distributed availability groups<\/a><\/blockquote><iframe sandbox=\"allow-scripts\" security=\"restricted\" src=\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-distributed-availability-groups\/embed\/#?secret=PHdrWDcNVd\" width=\"600\" height=\"338\" title=\"&#8220;SQL Server 2016 AlwaysOn: distributed availability groups&#8221; &#8212; dbi Blog\" data-secret=\"PHdrWDcNVd\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" class=\"wp-embedded-content\"><\/iframe><script type=\"text\/javascript\">\n\/* <![CDATA[ *\/\n\/*! This file is auto-generated *\/\n!function(d,l){\"use strict\";l.querySelector&&d.addEventListener&&\"undefined\"!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!\/[^a-zA-Z0-9]\/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret=\"'+t.secret+'\"]'),o=l.querySelectorAll('blockquote[data-secret=\"'+t.secret+'\"]'),c=new RegExp(\"^https?:$\",\"i\"),i=0;i<o.length;i++)o[i].style.display=\"none\";for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute(\"style\"),\"height\"===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):\"link\"===t.message&&(r=new URL(s.getAttribute(\"src\")),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener(\"message\",d.wp.receiveEmbedMessage,!1),l.addEventListener(\"DOMContentLoaded\",function(){for(var e,t,s=l.querySelectorAll(\"iframe.wp-embedded-content\"),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute(\"data-secret\"))||(t=Math.random().toString(36).substring(2,12),e.src+=\"#?secret=\"+t,e.setAttribute(\"data-secret\",t)),e.contentWindow.postMessage({message:\"ready\",secret:t},\"*\")},!1)))}(window,document);\n\/\/# sourceURL=https:\/\/www.dbi-services.com\/blog\/wp-includes\/js\/wp-embed.min.js\n\/* ]]> *\/\n<\/script>\n","thumbnail_url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-96-7-DAG-scenario-1.jpg","thumbnail_width":710,"thumbnail_height":500,"description":"This time, I will talk about distributed availability groups. What&#8217;s that? In short, a group of availability groups. Sounds good right? But in which cases may we need such architecture? Firstly, let\u2019s say that distributed availability groups will run on the top of two distinct availability groups meaning that they reside on two distinct WSFCs [&hellip;]"}