November 6, 2009 at 12:28 am
hi friends
in my company we are using sql server 2000 and apllication in same same server.. that application refer the database in same server
what is my problem
that application is vs 2003 ..when we running application some time its not working that time we need to restart IIS. then it is working fine ..daily we need to restart IIS more than 10 times ..we asked developers they are telling no problem in coding ..
so we thought to check database level
so i capture all information from profiler
now i need to take report like (time taking query or SP) and cpu usage
can any one help for report and IIS problem
Thanks
Yogi
November 6, 2009 at 2:07 am
Hi Yogi
First, if your problem becomes fixed when you restart IIS it does not appear to be a SQL Server problem ;-).
Could you explain more detailed the meaning of "not working"? (No response? Exceptions? Working slow?) Did you check profiler when your application was "not working"?
To catch long expensive or long running queries with Profiler use column filters for "Duration" and/or "CPU".
Greets
Flo
November 6, 2009 at 2:14 am
thanx Reischl
today only i started profiler against that server
now i am capturing full day process
not working means ---application page is coming unavailable
now i need to trace the time taking query and sP
November 6, 2009 at 2:22 am
Hi
Does "becomes unavailable" mean you get a timeout from web server?
To trace query/sp durations use Events:
* Stored Procedures/RPC:Completed
* SQL:BatchCompleted
Greets
Flo
November 6, 2009 at 2:28 am
ok thanx
i am checking profiler only now
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply