{"id":4033,"date":"2014-09-23T05:43:00","date_gmt":"2014-09-23T03:43:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/"},"modified":"2014-09-23T05:43:00","modified_gmt":"2014-09-23T03:43:00","slug":"sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/","title":{"rendered":"SQL Server 2014: classic commit vs commit with delayed durability & I\/Os"},"content":{"rendered":"

\"\"<\/p>\n

When you learn about SQL Server, you will often hear that a commit transaction is a synchronous operation and that you can trust it. In this blog post, I will provide some details about what we mean by synchronous behavior. The reason is that sometimes, when I talk about the new delayed durability feature provided by SQL Server 2014, there are some confusions. If you want more details on this new feature, please read the blog post of my colleague St\u00e9phane Haby here<\/a>. A quick shortcut is often the following: writing to the transaction log is synchronous, while writing with the new delayed durability feature is asynchronous.<\/p>\n

First of all, you probably know that the buffer manager guarantees that the transaction log is written before the changes to the database are written. This is the famous protocol called Write-Ahead logging (aka WAL). Log records are not written directly to disk but first into the buffer cache and then flushed to the disk in a purely asynchronous manner. However, at the commit time the related thread must wait for the writes to complete to the point of the commit log record in the transaction log. This is the synchronous part of commit operation in order to meet the WAL protocol.<\/p>\n

On the other hand, the new delayed durability feature allows the commit operation to be asynchronous (like writing to the transaction) but the big difference is that the related thread doesn\u2019t have to wait until the commit log record is written in the transaction log. This new feature introduces some performance improvements, but as a caveat, there is the loss of data.<\/p>\n

We can prove that both commit operations write asynchronously by using either the process monitor tool or by using a debugger and trying to catch the part of the code responsible for writing into the transaction log file.<\/p>\n

I will use the following T-SQL script for this demonstration:<\/p>\n

–> Commit transaction (without delayed durability option)<\/strong><\/p>\n

AdventureWorks2012;<\/span><\/span><\/div>\n
GO<\/span><\/div>\n
\u00a0<\/span><\/div>\n
— Ensure DELAYED_DURABILITY is OFF for this test <\/span><\/div>\n
ALTER DATABASE adventureworks2012 SET DELAYED_DURABILITY = DISABLED;<\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/div>\n
GO<\/span><\/div>\n
\u00a0<\/span><\/div>\n
— Create table t_tran_delayed_durability<\/span><\/div>\n
IF OBJECT_ID(N’t_tran_delayed_durability’, ‘U’) IS NOT NULL<\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DROP TABLE t_tran_delayed_durability;<\/span><\/span><\/span><\/span><\/div>\n
GO<\/span><\/div>\n
\u00a0<\/span><\/div>\n
\u00a0<\/span><\/div>\n
create table t_tran_delayed_durability<\/span><\/span><\/span><\/div>\n
(<\/span><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 id int identity<\/span><\/span><\/span><\/div>\n
);<\/span><\/div>\n
GO<\/span><\/div>\n
\u00a0<\/span><\/div>\n
— insert 1000 small transactions<\/span><\/div>\n
declare @i int = 1000<\/span><\/span><\/span><\/span><\/div>\n
\u00a0<\/span><\/div>\n
while @i 0<\/span><\/span><\/span><\/div>\n
begin<\/span><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 insert t_tran_delayed_durability default values<\/span><\/span><\/span><\/span><\/div>\n
\u00a0<\/span><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 set @i = @i – 1;<\/span><\/span><\/span><\/span><\/span><\/span><\/div>\n
end;<\/span><\/span><\/div>\n

 <\/p>\n

–> Commit transaction (with delayed durability enabled)<\/strong><\/p>\n

— Ensure DELAYED_DURABILITY is ON for this test <\/span><\/div>\n
ALTER DATABASE adventureworks2012 SET DELAYED_DURABILITY = ALLOWED;<\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/div>\n
GO<\/span><\/div>\n
\u00a0<\/span><\/div>\n
— Create table t_tran_delayed_durability<\/span><\/div>\n
IF OBJECT_ID(N’t_tran_delayed_durability’, ‘U’) IS NOT NULL<\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DROP TABLE t_tran_delayed_durability;<\/span><\/span><\/span><\/span><\/div>\n
GO<\/span><\/div>\n
\u00a0<\/span><\/div>\n
create table t_tran_delayed_durability<\/span><\/span><\/span><\/div>\n
(<\/span><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 id int identity<\/span><\/span><\/span><\/div>\n
);<\/span><\/div>\n
GO<\/span><\/div>\n
\u00a0<\/span><\/div>\n
— insert 1000 small transactions<\/span><\/div>\n
declare @i int = 1000<\/span><\/span><\/span><\/span><\/div>\n
\u00a0<\/span><\/div>\n
while @i 0<\/span><\/span><\/span><\/div>\n
begin<\/span><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 begin tran tran_1<\/span><\/span><\/span><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 insert t_tran_delayed_durability default values<\/span><\/span><\/span><\/span><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 commit tran tran_1 with (DELAYED_DURABILITY = on)<\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/div>\n
\u00a0<\/span><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 set @i = @i – 1;<\/span><\/span><\/span><\/span><\/span><\/div>\n
end;<\/span><\/span><\/div>\n

 <\/p>\n

Below, you will find an interesting picture of the process monitor trace output that shows the SQL Server file system activity that writes to the transaction log file in both cases.<\/p>\n

–> Commit transaction (without delayed durability option)<\/strong><\/p>\n

\"blog_17_1_procmon_normal_transaction\"<\/p>\n

You will notice that SQL Server uses the WriteFile() function to write to the transaction log for each commit operation (4096 bytes each). I will only show you a sample of the output, but you can imagine the final number of records you can have here. If we take a look at the process monitor stack you will notice that SQL Server uses the WriteFile() Windows function located in the Kernel32.lib library to write to the transaction log with an overlapped structure (in others words asynchronous I\/O).<\/p>\n

\"blog_17_3_procmon_stack\"<\/p>\n

This test confirms what Bob Dorr explains in the Microsoft article about SQL Server I\/Os and transaction log I\/O<\/a>.<\/p>\n

–> Commit transaction (with delayed durability enabled)<\/strong><\/p>\n

\"blog_17_1_procmon_delayed_transaction\"<\/p>\n

In this case, the same function is used by SQL Server with a big difference here: SQL Server will group some IO into chunks (in my case 16K, 48K, and 60K) before writing to disk. Cleary, there is less activity here (in my case 18 lines against approximatively 1000 lines for the first test).<\/p>\n

We can also attach a debugger (for instance WinDbg) to the SQL Server process and set a breakpoint in the Kernel32!writefile() function for the calling thread in order to have more details about the execution stack. Note that the process monitor stack showed the module KERNELBASE.dll for the WriteFile() function but as mentioned by this Microsoft article<\/a> kernelbase.dll gets functionality from kernel32.dll and advapi32.dll.<\/p>\n

\"blog_17_1_windbg_stack_writefile\"<\/p>\n

Both commit operations show the same stack except of course the number of executions.<\/p>\n

To summarize, I wanted to show you that both commit operations (with and without delayed duration) are using asynchronous IO to write to the transaction log file. The big difference is that with the delayed durability option, SQL Server improves the log IO writes performance by deferring and grouping the IO into 60K chunks before writing to the disk. I hope this will help you understand more about SQL Server commit operations.<\/p>\n

By David Barbarin<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

When you learn about SQL Server, you will often hear that a commit transaction is a synchronous operation and that you can trust it. In this blog post, I will provide some details about what we mean by synchronous behavior. The reason is that sometimes, when I talk about the new delayed durability feature provided […]<\/p>\n","protected":false},"author":26,"featured_media":3590,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[492,49,51,54,52],"type_dbi":[],"class_list":["post-4033","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-application-integration-middleware","tag-commit","tag-microsoft","tag-sql-server","tag-sql-server-2012","tag-sql-server-2014"],"acf":[],"yoast_head":"\nSQL Server 2014: classic commit vs commit with delayed durability & I\/Os - dbi Blog<\/title>\n<meta name=\"description\" content=\"When you learn about SQL Server, you will often hear that a commit transaction is a synchronous operation and that you can trust it. In this blog post, I will provide some details about what we mean by synchronous behavior.\" \/>\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-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Server 2014: classic commit vs commit with delayed durability & I\/Os\" \/>\n<meta property=\"og:description\" content=\"When you learn about SQL Server, you will often hear that a commit transaction is a synchronous operation and that you can trust it. In this blog post, I will provide some details about what we mean by synchronous behavior.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2014-09-23T03:43:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sqlserver2014.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"245\" \/>\n\t<meta property=\"og:image:height\" content=\"149\" \/>\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-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/\"},\"author\":{\"name\":\"Microsoft Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"headline\":\"SQL Server 2014: classic commit vs commit with delayed durability & I\/Os\",\"datePublished\":\"2014-09-23T03:43:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/\"},\"wordCount\":878,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sqlserver2014.jpg\",\"keywords\":[\"Commit\",\"Microsoft\",\"SQL Server\",\"SQL Server 2012\",\"SQL Server 2014\"],\"articleSection\":[\"Application integration & Middleware\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/\",\"name\":\"SQL Server 2014: classic commit vs commit with delayed durability & I\/Os - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sqlserver2014.jpg\",\"datePublished\":\"2014-09-23T03:43:00+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"description\":\"When you learn about SQL Server, you will often hear that a commit transaction is a synchronous operation and that you can trust it. In this blog post, I will provide some details about what we mean by synchronous behavior.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sqlserver2014.jpg\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sqlserver2014.jpg\",\"width\":245,\"height\":149},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Server 2014: classic commit vs commit with delayed durability & I\/Os\"}]},{\"@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 2014: classic commit vs commit with delayed durability & I\/Os - dbi Blog","description":"When you learn about SQL Server, you will often hear that a commit transaction is a synchronous operation and that you can trust it. In this blog post, I will provide some details about what we mean by synchronous behavior.","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-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/","og_locale":"en_US","og_type":"article","og_title":"SQL Server 2014: classic commit vs commit with delayed durability & I\/Os","og_description":"When you learn about SQL Server, you will often hear that a commit transaction is a synchronous operation and that you can trust it. In this blog post, I will provide some details about what we mean by synchronous behavior.","og_url":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/","og_site_name":"dbi Blog","article_published_time":"2014-09-23T03:43:00+00:00","og_image":[{"width":245,"height":149,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sqlserver2014.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-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/"},"author":{"name":"Microsoft Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"headline":"SQL Server 2014: classic commit vs commit with delayed durability & I\/Os","datePublished":"2014-09-23T03:43:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/"},"wordCount":878,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sqlserver2014.jpg","keywords":["Commit","Microsoft","SQL Server","SQL Server 2012","SQL Server 2014"],"articleSection":["Application integration & Middleware"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/","url":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/","name":"SQL Server 2014: classic commit vs commit with delayed durability & I\/Os - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sqlserver2014.jpg","datePublished":"2014-09-23T03:43:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"description":"When you learn about SQL Server, you will often hear that a commit transaction is a synchronous operation and that you can trust it. In this blog post, I will provide some details about what we mean by synchronous behavior.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sqlserver2014.jpg","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_sqlserver2014.jpg","width":245,"height":149},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2014-classic-commit-vs-commit-with-delayed-durability-and-ios\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL Server 2014: classic commit vs commit with delayed durability & I\/Os"}]},{"@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\/4033","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=4033"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/4033\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/3590"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=4033"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=4033"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=4033"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=4033"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}