Post reply

About TempDB issues

  • August 31, 2007 at 4:55 am

    #95391

    Hi there,

    As Microsoft and other suggest to split tempdb database, I followed the suggestion and after splitting into 4 files, I ran DBCC TRACEON (1118). But, 1 day after that, I ran DBCC TRACESTATUS (1118) and see that this trace flag is not nowhere enabled. What happens and why is disabled during night?

     

     

    In Theory, theory and practice are the same...In practice, they are not.

  • August 31, 2007 at 5:32 am

    #730714

    Sorin,

    DBCC TRACEON(1118) will turn on the traceflag for just the current

    connection, whereas including the flag as a startup parameter will apply it

    to ALL connections.

    Anyway I'm not sure I would use the trace flag since it changes the behaviour of your server and there have been several issues with this. Why don't you just create a couple of extra files for your tempdb by running a startup script.

    Markus

    [font="Verdana"]Markus Bohse[/font]

  • August 31, 2007 at 8:45 am

    #730805

    I know that this flag is for reading extents of 64 k, ok, I give up of this issue.

    In Theory, theory and practice are the same...In practice, they are not.

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

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