Post reply

Trace Flag 1118

  • January 20, 2013 at 8:04 am

    #273202

    Please share what helped shape your point of view on whether or not to enable TF 1118 in your SQL Server 2008 or 2008 R2 instances.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • January 20, 2013 at 8:12 am

    #1579025

    This trace flag helped me when I was working with SQL Server 2000 about 8 years ago. Since I've stopped working with SQL Server 2000, I did not have to use it.

    Adi

    --------------------------------------------------------------
    To know how to ask questions and increase the chances of getting asnwers:
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • January 20, 2013 at 11:17 am

    #1579034

    I'll only use it if I have TempDB contention and splitting the files doesn't help. Haven't needed it since SQL 2000.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • January 22, 2013 at 3:01 pm

    #1579840

    I found this article in which the author ran a test with 1 TempDB file. No performance gains were made.

    Also found this presentation on Trace Flags, contains section on Production Trace Flags, 1118 being one of them. References white paper.

Viewing 4 posts - 1 through 3 (of 3 total)

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