SQL Server Trace Flags - Complete list

Question

SQL Server Trace Flags - Complete list

Viewing 9 posts - 31 through 38 (of 38 total)

You must be logged in to reply to this topic. Login to reply

webrunner SSC-Dedicated Points: 31711 More actions · Answer 1

Thanks for this impressively comprehensive list!

- webrunner

-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html

przemyslawkus Grasshopper Points: 12 More actions · Answer 2

One more TF from Microsoft support (SQL Server 2012):

833 - disables superlatch

Needs SQL Services restart.

This reply was modified 4 years, 7 months ago by przemyslawkus.

Konstantin Taranov SSCertifiable Points: 6488 More actions · Answer 3

Hi, przemyslawkus. Thanks for this trace flag. Could you provide some extra information.

What is scope for this flag: session, global, query?

What is versions (except 2012) SQL Server it works?

Jeff Moden SSC Guru Points: 1003853 More actions · Answer 4

Alan Burstein wrote:

This article is awesome! Thanks for putting it together.

Alan, the migration to the "improved" SSC website has broken all of the links in your signature line.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Jeff Moden SSC Guru Points: 1003853 More actions · Answer 5

przemyslawkus wrote:

One more TF from Microsoft support (SQL Server 2012):
833 - disables superlatch
Needs SQL Services restart.

My recommendation would be not to use those types of trace flags. Instead, fix the code that's causing a problem because queries on larger data (and it's forever getting larger) may be adversely affected. Trace Flags are generally not meant to be a panacea of performance (there are exceptions but they are rare).

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

przemyslawkus Grasshopper Points: 12 More actions · Answer 6

@kast218, Scope: global. I don't know the versions of SQL Server unfortunately...

@jeff Moden: I don't say this is good to use, I am just sharing what was recommended by MS support as a workaround for a bug.

Konstantin Taranov SSCertifiable Points: 6488 More actions · Answer 7

przemyslawkus wrote:

One more TF from Microsoft support (SQL Server 2012):
833 - disables superlatch
Needs SQL Services restart.

Added, great thanks for new undocumented flag (just 2 flags left for 600).

https://github.com/ktaranov/sqlserver-kit/blob/master/SQL%20Server%20Trace%20Flag.md#833

sqL_handLe Newbie Points: 1 More actions · Answer 8

Hello! I've only tested in SQL Server 2019 but trace flag 835 no longer seems to disable LPIM.

romain.ferraton 82381 SSC Enthusiast Points: 116 More actions · Answer 9

I tried to classified official traceflags on a dashboard where you can search on topic like "cardinality" or "index" ==> https://www.architecture-performance.fr/ap_blog/sql-server-trace-flags-classification/