How to identify SQL Server busy?

  • On daily operations, sometime we do receive reports from users saying system slow for that period only. As an administrator, my action is use "sp_who" to find out if deadlock happen. Second thing is check "Memory Usage" in Enterprise Manager(Server Name>Management>Current Activity>Process Info). Is this an ideal practice? Anyone would like to share his experience?

  • You could also leave Profiler running and analyse the resulting trace around the 'slow' times to see whether you can identify what is causing the slowness (and therefore whether you can do something about it).


  • Run the trace from a remote server so that you can take off some load from the server.

  • Profiler is probably your best bet.

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

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