April 28, 2015 at 8:40 am
Hi Expert,
Today my Application server was too much slow , even user was not able to work on any application and cpu usage reached 100%, but compare to that Db server was fine and cpu usage was also normal.
We have restarted application server but after that the problem was still persist.
Then my manager has advised us to shut down first appliaction server then restart DB server then bring up application server.
After that activity the application are started working fine.
Here is my doubt, why CPU usage was not coming down when we restatred application server or recycle app pool. Why it came down after DB server restarted.
And what are the things I need to check when application server is too slow apart from server restarted activity.
Can anyone help me regarding this.
Thanks,
Arooj Ahmad
April 29, 2015 at 4:21 am
This could be so many things, given that your application server started responding quickly after the restart of the SQL Server, when the problem is occuring you need to start by looking at the following.
I am also assuming just on your initial post your not a DBA or that familar with SQL server so I'll try and keep it simple:
Use activity monitor within SQL server Management Studio to identify active proccess, you should be able to tell from here what queries are active and the resources they are taking up. This should help identify what exactly is happening.
It could be as simple that your application sever has made a call to the database that returns a very large volume of data which your appliction server could not cope with. By restarting the SQL server the request would have been killed and the application server would no longer have been receiving data.
MCITP SQL 2005, MCSA SQL 2012
April 29, 2015 at 4:51 am
Hi Taylor
Thanks for the support. But I did all the possibility what I could do in Sql Server like as you say , Activity Monitor, Sp_Who2 and I checked any query is blocking using some DMV query(sys.dm_tran_locks). But nothing was there . But yes I agree with your last statement that "lage number of volume has requested by app pool and after restatred that would have been killed." This could be possiblity for slowness.
Thanks
Arooj
April 29, 2015 at 4:58 am
You won't only be looking for blocking, for any active queries they may still have been executing, looking at the CPU \ Reads \ Duration of any active queries at that time would help identify a long running database call.
Also you should look at the waits on the SQL server. This will help identify if any queries etc are waiting on a resource.
MCITP SQL 2005, MCSA SQL 2012
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply