Post reply

Session id XX on Adventureworks is using 225.6 MB of space in tempdb. on IXXXXXSQL01

  • October 12, 2012 at 8:09 am

    #263870

    Hi folks,

    Session id XX on Adventureworks is using 225.6 MB of space in tempdb. on IXXXXXSQL01

    we have configured this kinda alerts in SQL server for monitoring. But I am not sure at such time what to do exactly after above alert triggers...

    what primary actions need to be taken....

    Sagar Sonawane
    ** Every DBA has his day!!:cool:

  • October 12, 2012 at 8:51 am

    #1548699

    Nothing probably.

    Is 200 MB of TempDB usage a problem? Is it excessive? Is it unusual?

    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

  • October 12, 2012 at 9:16 am

    #1548714

    GilaMonster (10/12/2012)

    Nothing probably.

    Is 200 MB of TempDB usage a problem? Is it excessive? Is it unusual?

    Hi Gail.... this is just context.... I mentioned about one session here .....apologies...

    I mean if there are multiple sessions occuring..... there ad deadlocs too.... what primary focus needs to be on as as DBA..... I hope you got my point.....

    Thank you Gail....

    Sagar Sonawane
    ** Every DBA has his day!!:cool:

  • October 12, 2012 at 9:50 am

    #1548742

    DBA should be focused on fixing or preventing problems. So, is the TempDB usage a problem?

    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 4 posts - 1 through 3 (of 3 total)

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