One Trace Flag a Day / SQL Server

Trace Flag 4199 Changes in SQL Server 2016 CTP2

- by Prince Rastogi - 2 Comments.

Hi Friends,

Microsoft announced various new features in SQL Server 2016 CTP2 release. One of the important features is related to Trace Flag 4199. This is the trace flag that was provided to combine various Query Optimizer related trace flags under a single trace flag. That means rather than enabling those multiple trace flags you can enable this single trace flag to overcome various Query Optimizer related issues. Trace flag 4199 covers various trace flags those comes under 41xx series.

In SQL Server 2016 CTP2, there is no need to enable this trace flag because in this version the behavior of trace flag 4199 has been enabled by default. The behavior of this Trace flag has been combined with compatibility level 130.  If you are using Compatibility level 130 then all the optimizer related hot-fixes released till SQL Server 2016 RTM will be enabled by default without trace flag 4199.

SQL Server 2016 Trace Flag 4199

   

Keep in mind that this behavior will not be applicable for the Optimizer related hotfixes released after SQL Server 2016 RTM version.

For more information about this trace flag you can click here.

HAPPY LEARNING!

Regards:
Prince Kumar Rastogi

Like us on FaceBook | Join the fastest growing SQL Server group on FaceBook

Follow Prince Rastogi on Twitter | Follow Prince Rastogi on FaceBook

   

Related Posts

Trace Flag 634 – Disable Background Columnstore Compression

SQL Server 2016 - Trace Flag 9453 - Disable Batch Mode Processing

SQL Server 2016 – Trace Flag 9453 – Disable Batch Mode Processing

SQL Server 2016 Trace Flag 2371 Change

About Prince Rastogi

Prince Rastogi is working as Database Administrator at Elephant Insurance, Richmond. He is having more than 8 years of experience and worked in ERP Domain, Wealth Management Domain. Currently he is working in Insurance domain. In the starting of his career he was working on SQL Server, Internet Information Server and Visual Source Safe. He is post graduate in Computer Science. Prince is ITIL certified professional. Prince likes to explore technical things for Database World and Writing Blogs. He is Technical Editor and Blogger at SQLServerGeeks.com. He is a regular speaker at DataPlatformDay events in Delhi NCR. He has also presented some in depth sessions about SQL Server in SQL Server Conferences in Bangalore.

View all posts by Prince Rastogi →

2 Comments on “Trace Flag 4199 Changes in SQL Server 2016 CTP2”

  2. I have the same question as Calin!

    I was exploring how the traceflag 4199 works but I see the same behavior with Compatibility level 120 and 130. Can you help me understand how is it different from SQL Server 2014?

    Reply

Leave a Reply

Your email address will not be published.