{"id":4901,"date":"2015-06-12T08:12:26","date_gmt":"2015-06-12T06:12:26","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/"},"modified":"2015-06-12T08:12:26","modified_gmt":"2015-06-12T06:12:26","slug":"sql-server-2016-availability-groups-and-the-new-option-db_failover","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/","title":{"rendered":"SQL Server 2016: availability groups and the new option DB_FAILOVER"},"content":{"rendered":"<div><img decoding=\"async\" class=\"blog-image aligncenter\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg\" alt=\"\" \/><\/div>\n<p>Let\u2019s continue the SQL Server 2016\u2019s discovery with one of my favourite topic: the AlwaysOn availability groups (AAGs). There are some improvements on this area.<\/p>\n<p>First of all, let\u2019s introduce one of them (DB_FAILOVER option) by remembering of the availability groups behaviour with the previous versions of SQL Server. One misconception that exists at different customer places is that an availability group doesn\u2019t detect a database failure. No, this not a joke but the pure reality. AAGs are designed only to detect issues at the SQL Server level instance until the introduction of SQL Server 2016. You can verify by yourself by looking at the different possible failover conditions levels.<\/p>\n<p>Indeed, SQL Server 2016 adds a new layer of failover capabilities with the new DB_FAILOVER option. According to the BOL, a new response will be taken by SQL Server when a database on the primary replica will be offline. Maybe, we must precise here what offline means: any status other than ONLINE for a database in the availability group will trigger an automatic failover. Keep in mind that this new feature is set on the group level. It means that all databases included to this group will be concerned by this option.<\/p>\n<p>During my session at the previous event <a href=\"http:\/\/guss.pro\/2014\/10\/27\/jss2014-infrastructure-et-always-on\/\">Journ\u00e9es SQL Server 2014<\/a> in Paris, I had the opportunity to show that no action was taken by the availability group for a database that had lost its transaction log. To be more precise, I simulated a scenario where the disk that contains the transaction log file has been lost. This is probably the most common scenario where we may encounter a database file failure. Let\u2019s perform the same today with SQL Server 2016.<\/p>\n<p>Let\u2019s begin with the creation script of the availability group 2016Grp. I put only the interesting part below:<\/p>\n<div>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">CREATE AVAILABILITY GROUP [2016Grp]\nWITH\n(\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 AUTOMATED_BACKUP_PREFERENCE = PRIMARY,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DB_FAILOVER = ON,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DTC_SUPPORT = NONE\n)\nFOR DATABASE [killerdb], [SSISDB]\nREPLICA ON N'SQL161'\nWITH\n(\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ENDPOINT_URL = N'TCP:\/\/SQL161.dbi-services.test:5022',\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 FAILOVER_MODE = AUTOMATIC,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 AVAILABILITY_MODE = SYNCHRONOUS_COMMIT,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 BACKUP_PRIORITY = 50,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SECONDARY_ROLE(ALLOW_CONNECTIONS = NO)\n),\nN'SQL162'\nWITH\n(\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ENDPOINT_URL = N'TCP:\/\/SQL162.dbi-services.test:5022',\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 FAILOVER_MODE = AUTOMATIC,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 AVAILABILITY_MODE = SYNCHRONOUS_COMMIT,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 BACKUP_PRIORITY = 50,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SECONDARY_ROLE(ALLOW_CONNECTIONS = NO)\n);\nGO<\/pre>\n<\/div>\n<p>&nbsp;<\/p>\n<p>This is a basic availability group with two replicas (SQL161 and SQL162) configured with synchronous replication and automatic failover that includes two databases named killerdb and SSISDB. You may notice the new options at the top of the script: DB_FAILOVER and DTC support that are available from the GUI as well:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog_49_-_4_-_alwayson_new_parameter_db_failover.jpg\" alt=\"blog_49_-_4_-_alwayson_new_parameter_db_failover\" width=\"549\" height=\"233\" \/><\/p>\n<p>Let\u2019s continue by creating a simple table dbo.t in the killerdb database and next, by inserting a bunch of data.<\/p>\n<p>&nbsp;<\/p>\n<div>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">USE killerdb;\nGO\n\u00a0\nCREATE TABLE dbo.t\n(\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 id INT NOT NULL IDENTITY(1,1)\n);\nGO\n\u00a0\nSET NOCOUNT ON;\nGO\n\u00a0\nINSERT dbo.t DEFAULT VALUES;\nGO 200\n\u00a0\nSELECT COUNT(*)\nFROM dbo.t;<\/pre>\n<\/div>\n<p>&nbsp;<\/p>\n<p>As expected the table contains 200 records.<\/p>\n<p>Now, it\u2019s time to unplug my disk from my computer that contains the killerdb transaction log file. After that, a new insertion of 200 additional rows raises the following error:<\/p>\n<div>Msg 9001, Level 21, State 3, Line 7<\/div>\n<div>The log for database &#8216;killerdb&#8217; is not available. Check the event log for related error messages. Resolve any errors and restart the database.<\/div>\n<div>Msg 0, Level 20, State 0, Line 6<\/div>\n<div>A severe error occurred on the current command. The results, if any, should be discarded.<\/div>\n<p>&nbsp;<\/p>\n<p>And good news! The availability group 2016Grp has switched automatically to the SQL162 replica in my case. Bear in mind that for one database failure, all the group will failover. Let\u2019s take a look at the AlwaysOn _health session:<\/p>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog_49_-_6_-_SQLDIAG_xel_file_detail.jpg\" alt=\"blog_49_-_6_-_SQLDIAG_xel_file_detail\" width=\"790\" height=\"113\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>You may see the response from the availability group against the error 1117 &#8211; I\/O \u2013 related to my unplugged disk event. On the new secondary the killerdb database is no longer online with the recovery pending state.<\/p>\n<div>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SELECT\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 @@SERVERNAME as server_name,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 name AS database_name,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 state_desc\nFROM sys.databases\nWHERE name = 'killerdb';\nGO<\/pre>\n<\/div>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog_49_-_7_-_killerdb_state.jpg\" alt=\"blog_49_-_7_-_killerdb_state\" width=\"339\" height=\"62\" \/><\/p>\n<p>This first improvement is surely a good way to enhance the global availability of the AlwaysOn availability group. We&#8217;ll discuss about the other interesting new options in the next blog posts.<br \/>\nStay connected!<\/p>\n<p>By David Barbarin<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Let\u2019s continue the SQL Server 2016\u2019s discovery with one of my favourite topic: the AlwaysOn availability groups (AAGs). There are some improvements on this area. First of all, let\u2019s introduce one of them (DB_FAILOVER option) by remembering of the availability groups behaviour with the previous versions of SQL Server. One misconception that exists at different [&hellip;]<\/p>\n","protected":false},"author":26,"featured_media":4856,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[199],"tags":[],"type_dbi":[],"class_list":["post-4901","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hardware-storage"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>SQL Server 2016: availability groups and the new option DB_FAILOVER - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Server 2016: availability groups and the new option DB_FAILOVER\" \/>\n<meta property=\"og:description\" content=\"Let\u2019s continue the SQL Server 2016\u2019s discovery with one of my favourite topic: the AlwaysOn availability groups (AAGs). There are some improvements on this area. First of all, let\u2019s introduce one of them (DB_FAILOVER option) by remembering of the availability groups behaviour with the previous versions of SQL Server. One misconception that exists at different [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2015-06-12T06:12:26+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"520\" \/>\n\t<meta property=\"og:image:height\" content=\"245\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Microsoft Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Microsoft Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/\"},\"author\":{\"name\":\"Microsoft Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"headline\":\"SQL Server 2016: availability groups and the new option DB_FAILOVER\",\"datePublished\":\"2015-06-12T06:12:26+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/\"},\"wordCount\":592,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg\",\"articleSection\":[\"Hardware &amp; Storage\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/\",\"name\":\"SQL Server 2016: availability groups and the new option DB_FAILOVER - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg\",\"datePublished\":\"2015-06-12T06:12:26+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg\",\"width\":520,\"height\":245},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Server 2016: availability groups and the new option DB_FAILOVER\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\",\"name\":\"Microsoft Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"caption\":\"Microsoft Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/microsoft-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"SQL Server 2016: availability groups and the new option DB_FAILOVER - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/","og_locale":"en_US","og_type":"article","og_title":"SQL Server 2016: availability groups and the new option DB_FAILOVER","og_description":"Let\u2019s continue the SQL Server 2016\u2019s discovery with one of my favourite topic: the AlwaysOn availability groups (AAGs). There are some improvements on this area. First of all, let\u2019s introduce one of them (DB_FAILOVER option) by remembering of the availability groups behaviour with the previous versions of SQL Server. One misconception that exists at different [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/","og_site_name":"dbi Blog","article_published_time":"2015-06-12T06:12:26+00:00","og_image":[{"width":520,"height":245,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg","type":"image\/jpeg"}],"author":"Microsoft Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Microsoft Team","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/"},"author":{"name":"Microsoft Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"headline":"SQL Server 2016: availability groups and the new option DB_FAILOVER","datePublished":"2015-06-12T06:12:26+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/"},"wordCount":592,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg","articleSection":["Hardware &amp; Storage"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/","url":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/","name":"SQL Server 2016: availability groups and the new option DB_FAILOVER - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg","datePublished":"2015-06-12T06:12:26+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sql2016.jpg","width":520,"height":245},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-availability-groups-and-the-new-option-db_failover\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL Server 2016: availability groups and the new option DB_FAILOVER"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4","name":"Microsoft Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","caption":"Microsoft Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/microsoft-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/4901","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=4901"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/4901\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/4856"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=4901"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=4901"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=4901"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=4901"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}