{"id":8450,"date":"2016-06-28T09:34:27","date_gmt":"2016-06-28T07:34:27","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/"},"modified":"2016-06-28T09:34:27","modified_gmt":"2016-06-28T07:34:27","slug":"trace-flag-4199-or-not-in-sql-server-2016","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/","title":{"rendered":"Trace Flag 4199 or not in SQL Server 2016?"},"content":{"rendered":"<p>Some Trace Flag like T1117 and T1118 are no more needed as you can read on <a href=\"http:\/\/dbi-services.com\/blog\/sql-server-2016-new-database-scoped-configuration-parameters\/\" target=\"_blank\" rel=\"noopener\">David&#8217;s blog<\/a>.<br \/>\nBut that&#8217;s not all, you have also the T4199&#8230;<\/p>\n<h3>What&#8217; does the Trace Flag T4199?<\/h3>\n<p>This Trace Flag enables all query optimizer fixes.<br \/>\nA lot of DBAs have enabled this Trace Flag globally during the build of a new server.<br \/>\nIf you want to take advantage of an enhancement or a fix, the T4199 becomes a necessity&#8230;<\/p>\n<p>But now, with SQL Server 2016, this is an old story!<\/p>\n<h3>SQL Server 2016 eliminates the T4199<\/h3>\n<p>In SQL Server 2016, you don&#8217;t need to enable this Trace Flag, forget your old habit!<br \/>\nIt is automatically included when you change the COMPATIBILY LEVEL to 130:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">USE [master]\nGO\nALTER DATABASE [MyDatabase] SET COMPATIBILITY_LEVEL = 130\nGO\n\n<\/pre>\n<p><strong>Advise:<\/strong> If you find a unexpected\/poor plan, use the Query Store to analyze and force a plan!<br \/>\nMore information on the <a href=\"https:\/\/support.microsoft.com\/en-us\/kb\/974006\" target=\"_blank\" rel=\"noopener\">KB974006<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Some Trace Flag like T1117 and T1118 are no more needed as you can read on David&#8217;s blog. But that&#8217;s not all, you have also the T4199&#8230; What&#8217; does the Trace Flag T4199? This Trace Flag enables all query optimizer fixes. A lot of DBAs have enabled this Trace Flag globally during the build of [&hellip;]<\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[48],"tags":[49,51,566,787],"type_dbi":[],"class_list":["post-8450","post","type-post","status-publish","format-standard","hentry","category-technology-survey","tag-microsoft","tag-sql-server","tag-sql-server-2016","tag-traceflag"],"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>Trace Flag 4199 in SQLServer 2016<\/title>\n<meta name=\"description\" content=\"SQL Server 2016 need no more the Trace Flag 4199.\" \/>\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\/trace-flag-4199-or-not-in-sql-server-2016\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Trace Flag 4199 or not in SQL Server 2016?\" \/>\n<meta property=\"og:description\" content=\"SQL Server 2016 need no more the Trace Flag 4199.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-06-28T07:34:27+00:00\" \/>\n<meta name=\"author\" content=\"St\u00e9phane Haby\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"St\u00e9phane Haby\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"1 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/\"},\"author\":{\"name\":\"St\u00e9phane Haby\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/d0bfb7484ae81c8980fc2b11334f803b\"},\"headline\":\"Trace Flag 4199 or not in SQL Server 2016?\",\"datePublished\":\"2016-06-28T07:34:27+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/\"},\"wordCount\":149,\"commentCount\":0,\"keywords\":[\"Microsoft\",\"SQL Server\",\"SQL Server 2016\",\"traceflag\"],\"articleSection\":[\"Technology Survey\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/\",\"name\":\"Trace Flag 4199 in SQLServer 2016\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2016-06-28T07:34:27+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/d0bfb7484ae81c8980fc2b11334f803b\"},\"description\":\"SQL Server 2016 need no more the Trace Flag 4199.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Trace Flag 4199 or not in SQL Server 2016?\"}]},{\"@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\/d0bfb7484ae81c8980fc2b11334f803b\",\"name\":\"St\u00e9phane Haby\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g\",\"caption\":\"St\u00e9phane Haby\"},\"description\":\"St\u00e9phane Haby has more than ten years of experience in Microsoft solutions. He is specialized in SQL Server technologies such as installation, migration, best practices, and performance analysis etc. He is also an expert in Microsoft Business Intelligence solutions such as SharePoint, SQL Server and Office. Futhermore, he has many years of .NET development experience in the banking sector and other industries. In France, he was one of the first people to have worked with Microsoft Team System. He has written several technical articles on this subject. St\u00e9phane Haby is Microsoft Most Valuable Professional (MVP) as well as Microsoft Certified Solutions Associate (MCSA) and\u00a0Microsoft Certified Solutions Expert (MCSE) for SQL Server 2012. He is also Microsoft Certified Technology Specialist (MCTS) and Microsoft Certified IT Professional (MCITP) for SQL Server 2008 as well as ITIL Foundation V3 certified. He holds a Engineer diploma in industrial computing and automation from France. His branch-related experience covers Chemicals &amp; Pharmaceuticals, Banking \/ Financial Services, and many other industries.\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/stephane-haby\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Trace Flag 4199 in SQLServer 2016","description":"SQL Server 2016 need no more the Trace Flag 4199.","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\/trace-flag-4199-or-not-in-sql-server-2016\/","og_locale":"en_US","og_type":"article","og_title":"Trace Flag 4199 or not in SQL Server 2016?","og_description":"SQL Server 2016 need no more the Trace Flag 4199.","og_url":"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/","og_site_name":"dbi Blog","article_published_time":"2016-06-28T07:34:27+00:00","author":"St\u00e9phane Haby","twitter_card":"summary_large_image","twitter_misc":{"Written by":"St\u00e9phane Haby","Est. reading time":"1 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/"},"author":{"name":"St\u00e9phane Haby","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/d0bfb7484ae81c8980fc2b11334f803b"},"headline":"Trace Flag 4199 or not in SQL Server 2016?","datePublished":"2016-06-28T07:34:27+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/"},"wordCount":149,"commentCount":0,"keywords":["Microsoft","SQL Server","SQL Server 2016","traceflag"],"articleSection":["Technology Survey"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/","url":"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/","name":"Trace Flag 4199 in SQLServer 2016","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2016-06-28T07:34:27+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/d0bfb7484ae81c8980fc2b11334f803b"},"description":"SQL Server 2016 need no more the Trace Flag 4199.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/trace-flag-4199-or-not-in-sql-server-2016\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Trace Flag 4199 or not in SQL Server 2016?"}]},{"@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\/d0bfb7484ae81c8980fc2b11334f803b","name":"St\u00e9phane Haby","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1123227ca39a5dca608c0f72d23cd1904fee29979749bbb3a485b9438436c553?s=96&d=mm&r=g","caption":"St\u00e9phane Haby"},"description":"St\u00e9phane Haby has more than ten years of experience in Microsoft solutions. He is specialized in SQL Server technologies such as installation, migration, best practices, and performance analysis etc. He is also an expert in Microsoft Business Intelligence solutions such as SharePoint, SQL Server and Office. Futhermore, he has many years of .NET development experience in the banking sector and other industries. In France, he was one of the first people to have worked with Microsoft Team System. He has written several technical articles on this subject. St\u00e9phane Haby is Microsoft Most Valuable Professional (MVP) as well as Microsoft Certified Solutions Associate (MCSA) and\u00a0Microsoft Certified Solutions Expert (MCSE) for SQL Server 2012. He is also Microsoft Certified Technology Specialist (MCTS) and Microsoft Certified IT Professional (MCITP) for SQL Server 2008 as well as ITIL Foundation V3 certified. He holds a Engineer diploma in industrial computing and automation from France. His branch-related experience covers Chemicals &amp; Pharmaceuticals, Banking \/ Financial Services, and many other industries.","url":"https:\/\/www.dbi-services.com\/blog\/author\/stephane-haby\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8450","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\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=8450"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8450\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=8450"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=8450"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=8450"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=8450"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}