Home Forums SQL Server 2014 Administration - SQL Server 2014 Can't release space of temdb RE: Can't release space of temdb

  • September 4, 2015 at 8:39 am

    #1824692

    Alvin Ramard (9/4/2015)

    Jeff Moden (9/3/2015)

    sriponraj (9/3/2015)

    Check the connection for temp db by using sp_who2 active. Kill all the connection related to temp db and try to shrink..

    So, if the run you kill is the one that processes your payroll hours, how ya going to feel about that? 😉

    Killing SPIDs is a bad idea.

    Sometimes you have to kill SPIDs. Killing SPIDs without knowing what you're killing is a bad idea indeed.

    FYI, that idea was posted by a newbie who apparently didn't really take into consideration what had already been discussed, so .... 😎

    Agreed that you sometimes need to kill spids but not so you can shrink TempDB. If you're going to do that, you might as well bounce the server. A close second would be to set the server to single user with rollback immediate. Too many things use TempDB to chase spids that are using TempDB.

    Understood on the newbie thing, as well.

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