SQL Server Performance

proc cache dive

Discussion in 'ALL SQL SERVER QUESTIONS' started by timscronin, Dec 20, 2011.

  1. timscronin New Member

    I had a 3rd party app have page life and proc cache, both take a dive yesterday, at the same time work tables went through the roof. At home sick so came in, issue was gone when I arrived. COnsidering these circumstances (no blocking at this time) what would be the best way to look at a culprit and would the dmv's be able to help me today?
  2. Luis Martin Moderator

    Any job running at that time?
  3. SQLTentMaker New Member

    Ultimately you are going to need to do some collection of queries in order to get that information being that it is historical. You might be able to find it when looking at expensive queries that need indexes and see what generated a ton of reads as that is most likely going to be the symptom for this issue.

    Hope this helps.
  4. satya Moderator

    Best thing to check TEMPDB size, blocking, log size on the databases to see why the issue touched the fan.
    You can go through about few reports on SQL Management studio to get some ifnormation.

Share This Page