{"id":7402,"date":"2016-03-17T21:48:07","date_gmt":"2016-03-17T20:48:07","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/"},"modified":"2016-03-17T21:48:07","modified_gmt":"2016-03-17T20:48:07","slug":"sql-server-2016-new-database-scoped-configuration-parameters","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/","title":{"rendered":"SQL Server 2016: new database-scoped configuration parameters"},"content":{"rendered":"

Do you remember new capabilities shipped with SQL Server 2016 CTP2 about tempdb? In this blog post<\/a>, I talked about well-known trace flags 1117 and 1118 that become useless for tempdb because their related effects are automatically applied to tempdb.<\/p>\n

Another interesting news that comes from the new SQL Server 2016 RC0 is the use of new database-scoped parameters AUTOGROW_SINGLE_FILE \/ AUTOGROW_ALL_FILES as well as MIXED_PAGE_ALLOCATION that will replace respectively the effects of the 1117 and 1118 trace flags for a particular database. This is a very great news because we will benefit of a more granular configuration regarding our specific workload against one particular database.<\/p>\n

Let\u2019s create this simple database and let\u2019s enable the AUTOGROW_ALL_FILES on the primary filegroup<\/p>\n

CREATE DATABASE [DB_2016]\n ON  PRIMARY \n( NAME = N'DB_2016', FILENAME = N'E:\\SQLSERVER\\SQL16\\DB_2016.mdf' , SIZE = 524288KB , FILEGROWTH = 65536KB ),\n( NAME = N'DB_20162', FILENAME = N'E:\\SQLSERVER\\SQL16\\DB_20162.ndf' , SIZE = 524288KB , FILEGROWTH = 65536KB ),\n( NAME = N'DB_20163', FILENAME = N'E:\\SQLSERVER\\SQL16\\DB_20163.ndf' , SIZE = 524288KB , FILEGROWTH = 65536KB )\n LOG ON \n( NAME = N'DB_2016_log', FILENAME = N'F:\\SQLSERVER\\SQL16\\DB_2016_log.ldf' , SIZE = 524288KB , FILEGROWTH = 65536KB )\nGO\n\nALTER DATABASE [DB_2016]\nMODIFY FILEGROUP [PRIMARY] AUTOGROW_ALL_FILES;\nGO<\/pre>\n
 <\/p>\n
The sys.filegroups<\/em> system view has a new is_autogrow_files<\/em> column to check if all files in the same filegroup will grow at the same time<\/p>\n
USE [DB_2016];\nGO\n\nSELECT \n\tDB_NAME() AS [db_name],\n\tmf.name AS logical_name,\n\tfg.name as [filegroup_name],\n\tfg.is_autogrow_all_files\nFROM sys.database_files AS mf\nJOIN sys.filegroups AS fg\n\tON mf.data_space_id = fg.data_space_id\nGO<\/pre>\n
 <\/p>\n
\"blog<\/a><\/p>\n
Let’s validate this new option with the following pretty simple test:<\/p>\n
CREATE TABLE dbo.test_2016\n(\n\tid INT IDENTITY,\n\tcol1 CHAR(8000) DEFAULT 'T'\n);\nGO\n\nINSERT INTO dbo.test_2016 DEFAULT VALUES;\nGO 210000<\/pre>\n
 <\/p>\n
File sizes have increased as expected by refering to the following query output:<\/p>\n
SELECT \n\tname AS logical_name,\n\tsize \/ 128 AS size_mb,\n\tCAST(FILEPROPERTY(name, 'SpaceUsed') * 100. \/ size AS DECIMAL(5, 2)) AS [%_free]\nFROM sys.database_files\nWHERE type_desc = 'ROWS'<\/pre>\n
 <\/p>\n
\"blog<\/a><\/p>\n
All files seem to have grown with the same target size at the same time according to events found in the default trace.<\/p>\n
DECLARE @path NVARCHAR(260);\n\nSELECT \n   @path = REVERSE(SUBSTRING(REVERSE([path]), \n   CHARINDEX('\\', REVERSE([path])), 260)) + N'log.trc'\nFROM    sys.traces\nWHERE   is_default = 1;\n\nSELECT \n   DatabaseName,\n   [FileName],\n   SPID,\n   Duration,\n   StartTime,\n   EndTime,\n   FileType = CASE EventClass \n       WHEN 92 THEN 'Data'\n       WHEN 93 THEN 'Log'\n   END\nFROM sys.fn_trace_gettable(@path, DEFAULT)\nWHERE EventClass = 92\n\tAND DatabaseName = 'DB_2016'\nORDER BY StartTime DESC;<\/pre>\n
 <\/p>\n
\"blog<\/a><\/p>\n
In the next scenario, let\u2019s test the effect of the second interesting MIXED_PAGE_ALLOCATION option. Let\u2019s say we want to disable the allocation of mixed extents (default behavior) by using the following command:<\/p>\n
ALTER DATABASE [DB_2016] SET MIXED_PAGE_ALLOCATION OFF;\nGO<\/pre>\n
 <\/p>\n
As the previous database-scoped option we are able to control which databases are candidate for mixed or uniform allocations by default. This information is directly accessible from the sys.databases<\/em> DMV as shown below:<\/p>\n
SELECT \n\tname, is_mixed_page_allocation_on\nFROM sys.databases<\/pre>\n
 <\/p>\n
\"blog<\/a><\/p>\n
You may notice that we are now able to confirm that mixed extent allocation is disabled by default for our user database and tempdb as well (without enabling the trace flag 1118).<\/p>\n
Let\u2019s perform the quick test of verifying if uniform extend is the default behavior for the DB_2016 database (my database is in SIMPLe recovery model here)<\/p>\n
CHECKPOINT;\n\nCREATE TABLE dbo.test_20161\n(\n\tid INT IDENTITY,\n\tcol1 CHAR(8000) DEFAULT 'T'\n);\nGO\n\nINSERT INTO dbo.test_20161 DEFAULT VALUES;\nGO 1<\/pre>\n
Let\u2019s verify the context of the DB_2016 database transaction log. We may notice the related record that confirms a new uniform extent is allocated of the concerned dbo.test_20161<\/em> table as shown below:<\/p>\n
\"blog<\/a><\/p>\n
We may also double check by using the sys.dm_db_database_page_allocations<\/em> DMF against the same table as following:<\/p>\n
SELECT \n\tOBJECT_NAME(object_id) AS table_name,\n\tindex_id,\n\t[partition_id],\n\textent_page_id,\n\tallocated_page_page_id,\n\tpage_type_desc as page_type\nFROM sys.dm_db_database_page_allocations(DB_ID(), OBJECT_ID('dbo.test_20161'), 0, NULL, 'DETAILED')<\/pre>\n
 <\/p>\n
\"blog<\/a><\/p>\n
Stay tuned! In the next blog we\u2019ll see other interesting database-scoped options provided with the future release of SQL Server 2016.<\/p>\n
By David Barbarin<\/p>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
Do you remember new capabilities shipped with SQL Server 2016 CTP2 about tempdb? In this blog post, I talked about well-known trace flags 1117 and 1118 that become useless for tempdb because their related effects are automatically applied to tempdb. Another interesting news that comes from the new SQL Server 2016 RC0 is the use […]<\/p>\n","protected":false},"author":26,"featured_media":7409,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[595,775,776,777,778,779,780,566,781],"type_dbi":[],"class_list":["post-7402","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","tag-autogrow","tag-autogrow_all_files","tag-autogrow_single_file","tag-database-scoped-parameters","tag-mixed-extent","tag-mixed_page_allocation","tag-page-allocation","tag-sql-server-2016","tag-uniform-extent"],"acf":[],"yoast_head":"\nSQL Server 2016: new database-scoped configuration parameters<\/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-new-database-scoped-configuration-parameters\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Server 2016: new database-scoped configuration parameters\" \/>\n<meta property=\"og:description\" content=\"Do you remember new capabilities shipped with SQL Server 2016 CTP2 about tempdb? In this blog post, I talked about well-known trace flags 1117 and 1118 that become useless for tempdb because their related effects are automatically applied to tempdb. Another interesting news that comes from the new SQL Server 2016 RC0 is the use […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-03-17T20:48:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-84-1-AUTOGROW_ALL_FILES-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"467\" \/>\n\t<meta property=\"og:image:height\" content=\"100\" \/>\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=\"4 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-new-database-scoped-configuration-parameters\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/\"},\"author\":{\"name\":\"Microsoft Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"headline\":\"SQL Server 2016: new database-scoped configuration parameters\",\"datePublished\":\"2016-03-17T20:48:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/\"},\"wordCount\":422,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-84-1-AUTOGROW_ALL_FILES-1.jpg\",\"keywords\":[\"autogrow\",\"AUTOGROW_ALL_FILES\",\"AUTOGROW_SINGLE_FILE\",\"database scoped parameters\",\"mixed extent\",\"MIXED_PAGE_ALLOCATION\",\"page allocation\",\"SQL Server 2016\",\"uniform extent\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/\",\"name\":\"SQL Server 2016: new database-scoped configuration parameters\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-84-1-AUTOGROW_ALL_FILES-1.jpg\",\"datePublished\":\"2016-03-17T20:48:07+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-84-1-AUTOGROW_ALL_FILES-1.jpg\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-84-1-AUTOGROW_ALL_FILES-1.jpg\",\"width\":467,\"height\":100},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Server 2016: new database-scoped configuration parameters\"}]},{\"@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: new database-scoped configuration parameters","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-new-database-scoped-configuration-parameters\/","og_locale":"en_US","og_type":"article","og_title":"SQL Server 2016: new database-scoped configuration parameters","og_description":"Do you remember new capabilities shipped with SQL Server 2016 CTP2 about tempdb? In this blog post, I talked about well-known trace flags 1117 and 1118 that become useless for tempdb because their related effects are automatically applied to tempdb. Another interesting news that comes from the new SQL Server 2016 RC0 is the use […]","og_url":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/","og_site_name":"dbi Blog","article_published_time":"2016-03-17T20:48:07+00:00","og_image":[{"width":467,"height":100,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-84-1-AUTOGROW_ALL_FILES-1.jpg","type":"image\/jpeg"}],"author":"Microsoft Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Microsoft Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/"},"author":{"name":"Microsoft Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"headline":"SQL Server 2016: new database-scoped configuration parameters","datePublished":"2016-03-17T20:48:07+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/"},"wordCount":422,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-84-1-AUTOGROW_ALL_FILES-1.jpg","keywords":["autogrow","AUTOGROW_ALL_FILES","AUTOGROW_SINGLE_FILE","database scoped parameters","mixed extent","MIXED_PAGE_ALLOCATION","page allocation","SQL Server 2016","uniform extent"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/","url":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/","name":"SQL Server 2016: new database-scoped configuration parameters","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-84-1-AUTOGROW_ALL_FILES-1.jpg","datePublished":"2016-03-17T20:48:07+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-84-1-AUTOGROW_ALL_FILES-1.jpg","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-84-1-AUTOGROW_ALL_FILES-1.jpg","width":467,"height":100},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL Server 2016: new database-scoped configuration parameters"}]},{"@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\/7402","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=7402"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/7402\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/7409"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=7402"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=7402"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=7402"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=7402"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}