TempDB full

  • if Temp Db full which databases will go Offline?

  • No databases will go offline. It wil generate error level 17 messages stating "object xx can't be created in filegroup yy for database TempDB" and the transaction(s) will be cancelled and rolled back.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
  • HanShi (5/14/2013)


    No databases will go offline. It wil generate error level 17 messages stating "object xx can't be created in filegroup yy for database TempDB" and the transaction(s) will be cancelled and rolled back.

    Unless it happens during a restart. If tempdb does not have enough space to growth, SQL won't start.

  • HanShi (5/14/2013)


    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

    I absolutely love that quote.

    --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 (5/14/2013)


    HanShi (5/14/2013)


    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

    I absolutely love that quote.

    Thanks Jeff.

    And especially on the internet this is a phrase to live by! :w00t:

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
  • sql-lover (5/14/2013)


    HanShi (5/14/2013)


    No databases will go offline. It wil generate error level 17 messages stating "object xx can't be created in filegroup yy for database TempDB" and the transaction(s) will be cancelled and rolled back.

    Unless it happens during a restart. If tempdb does not have enough space to growth, SQL won't start.

    If TempDB cannot be recreated, SQL will not start. That would required that someone shuts down SQL, deletes the tempDB files and then does something to fill the disk before restarting SQL. Otherwise the TempDB files will already exist at the time of startup (and they're not grown during the startup process, they're set back to their initial size)

    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

Viewing 6 posts - 1 through 5 (of 5 total)

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