Post reply

SQL Server Trace Flags - Complete list

  • February 23, 2017 at 12:03 am

    #320668

    Comments posted to this topic are about the item SQL Server Trace Flags - Complete list

  • February 23, 2017 at 2:19 am

    #1929896

    Mr. Taranov this is an amazing article. Very very useful.

    Br. Kenneth Igiri
    https://kennethigiri.com
    All nations come to my light, all kings to the brightness of my rising

  • February 23, 2017 at 3:14 am

    #1929898

    Br. Kenneth Igiri - Thursday, February 23, 2017 2:19 AM

    Mr. Taranov this is an amazing article. Very very useful.

    Thank you for your feedback! We maintained and updated this list regularly on Github

    If you find some typos, errors, mistakes or some enchantments - please post anywhere: here, email me or (best option create issue on Github or pull request)

  • February 23, 2017 at 5:44 am

    #1929916

    awesome, added to favorites

    -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle

  • February 23, 2017 at 5:45 am

    #1929917

    VERY useful.  Thank you for taking the time to put it together.

    On TF 8666... the description is a bit unremarkable as to what it can actually be used for.  For example, one of the things that it causes to be included in execution plans are the names of the stats it used to come up with the plan.  Using a bit o' XML magic and over time, it allows you to clearly identify which stats are actually in use so that you can delete unused stats.

    --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)

  • February 23, 2017 at 7:47 am

    #1929952

    Excellent! Very useful info. Thanks a lot.

  • February 23, 2017 at 9:11 am

    #1929971

    Jeff Moden - Thursday, February 23, 2017 5:45 AM

    VERY useful.  Thank you for taking the time to put it together.

    On TF 8666... the description is a bit unremarkable as to what it can actually be used for.  For example, one of the things that it causes to be included in execution plans are the names of the stats it used to come up with the plan.  Using a bit o' XML magic and over time, it allows you to clearly identify which stats are actually in use so that you can delete unused stats.

    Jeff, great thanks for your answer, added to github. Be free to add pull request or just post a new comment.

  • February 23, 2017 at 9:12 am

    #1929973

    SQL Guy 1 - Thursday, February 23, 2017 7:47 AM

    Excellent! Very useful info. Thanks a lot.

    Thanks!

  • February 23, 2017 at 2:15 pm

    #1930048

    Fantastic compilation. Thanks Taranov!

  • February 23, 2017 at 7:55 pm

    #1930086

    kast218 - Thursday, February 23, 2017 9:11 AM

    Jeff Moden - Thursday, February 23, 2017 5:45 AM

    VERY useful.  Thank you for taking the time to put it together.

    On TF 8666... the description is a bit unremarkable as to what it can actually be used for.  For example, one of the things that it causes to be included in execution plans are the names of the stats it used to come up with the plan.  Using a bit o' XML magic and over time, it allows you to clearly identify which stats are actually in use so that you can delete unused stats.

    Jeff, great thanks for your answer, added to github. Be free to add pull request or just post a new comment.

    I cannot take the credit for it.  The man in the following article deserves the credit.  It's a fantastic article if you're having problems with too many stats and need to find what they are.
    https://blogfabiano.com/2012/07/03/statistics-used-in-a-cached-query-plan/

    --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)

  • February 24, 2017 at 12:26 pm

    #1930248

    Jeff Moden - Thursday, February 23, 2017 5:45 AM

    VERY useful.  Thank you for taking the time to put it together.

    On TF 8666... the description is a bit unremarkable as to what it can actually be used for.  For example, one of the things that it causes to be included in execution plans are the names of the stats it used to come up with the plan.  Using a bit o' XML magic and over time, it allows you to clearly identify which stats are actually in use so that you can delete unused stats.

    very useful information there Jeff.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • February 25, 2017 at 11:00 am

    #1930332

    SQLRNNR - Friday, February 24, 2017 12:26 PM

    Jeff Moden - Thursday, February 23, 2017 5:45 AM

    VERY useful.  Thank you for taking the time to put it together.

    On TF 8666... the description is a bit unremarkable as to what it can actually be used for.  For example, one of the things that it causes to be included in execution plans are the names of the stats it used to come up with the plan.  Using a bit o' XML magic and over time, it allows you to clearly identify which stats are actually in use so that you can delete unused stats.

    very useful information there Jeff.

    Again, though, I can't take the credit for it.  I learned it on the following link.  I have tested it on my busy server but haven't yet implemented the "capture over time" part of it.  On that busy server and despite the size and huge number of execution plans, it only takes about 10 minutes to execute and does so without much interference..
    https://blogfabiano.com/2012/07/03/statistics-used-in-a-cached-query-plan/

    --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)

  • February 26, 2017 at 4:44 pm

    #1930397

    That's quite a list - and very useful.  I especially like the links for more information on each one.  Thanks for posting it.

    Tally Tables - Performance Personified
    String Splitting with True Performance
    Best practices on how to ask questions

  • March 1, 2017 at 8:07 am

    #1930972

    Ed Wagner - Sunday, February 26, 2017 4:44 PM

    That's quite a list - and very useful.  I especially like the links for more information on each one.  Thanks for posting it.

    Thanks for feedback!

  • March 1, 2017 at 10:14 pm

    #1931097

    Link to github seems to be broken.
    But the one you posted in this thread is Ok.

    Thanks!

Viewing 15 posts - 1 through 15 (of 38 total)

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