Post reply

performance tuning

  • July 2, 2010 at 2:56 am

    #223477

    if i get error like tempdb is full and i tried to shink it bt after shrnkng it nt releasing spcae, i found properties ahve negetive value.

    i wanna knw the negetive value of database property what shows??

  • July 2, 2010 at 3:29 am

    #1188085

    DBCC UPDATEUSAGE

    run it in the context of TempDB.

    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

  • July 2, 2010 at 3:53 am

    #1188091

    sir, i wanna knw what does the negetive value shows? and how they become negetive and how can i see those?

    thank you

  • July 2, 2010 at 4:04 am

    #1188094

    Most likely bugs in the code that maintains the page allocations.

    Are you really running SQL 2008? those bugs should all be fixed in 2008, they were prevalent and common on 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

  • July 2, 2010 at 4:07 am

    #1188095

    p.s Why are you shrinking TempDB? If you're getting errors about tempDB full, it means that it needs to be bigger, not smaller. Shrinking is likely making the problem worse.

    Either grow TempDB or investigate what queries are filling it and fix them.

    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

  • July 2, 2010 at 4:17 am

    #1188096

    if i dont have more space in my drive thn???

  • July 2, 2010 at 5:06 am

    #1188109

    Then investigate what's causing tempDB to grow and fix the root cause. Trying to shrink a database that needs to grow is not a solution.

    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

  • July 2, 2010 at 5:12 am

    #1188112

    somebody suggested move database from one place to another

    will it help n if yes then why???

  • July 2, 2010 at 6:24 am

    #1188136

    sachinsoni84 (7/2/2010)

    somebody suggested move database from one place to another

    will it help n if yes then why???

    You would only move to another location if that other location is bigger. More space solves the problem of running out of space. However, it doesn't address Gail's point about identifying the fundamental problem that is causing the extreme growth and fixing that, rather than trying to tweak the space constantly.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • July 2, 2010 at 6:41 am

    #1188148

    How large was tempdb when you shrank it? I separate tempdb out to it's own drive and start with a small amount of space with the anticipation that I can grow that drive if necessary and/or move the tempdb if I must.

    lavigne

    @wcucomputernerd

    http://www.sqlfornewbies.com

Viewing 10 posts - 1 through 10 (of 10 total)

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