April 28, 2013 at 3:25 pm
Hello,
One of my clients has a few web applications using SQL Server as a backend. One of those applications in particular has a performance problem, namely that logins are taking 10-15 seconds. I need to troubleshoot the issue to first identify whether this issue is related to SQL Server, or something else such as the web server. How can one go about troubleshooting this to identify where the issue lies? Are there any tools or techniques I can use to do this?
Thanks !
April 28, 2013 at 9:47 pm
Since this is a SQL Server forum, I'll concentrate on SQL Server only, but in reality this investigation should start from the application-end and work down the application stack.
With SQL profiler running, take a baseline of the round trip time from client request to client render complete.
See what queries and procs are being run to build that page, and see how long those queries take as a % of the total round trip.
April 29, 2013 at 1:04 am
You might want to compare the time difference while doing dome operation on your webpage and running the underlying query on sql server to check if there is some issue on SQL side or some other stuff. If you don't know what is underlying query to the page (which is very rare case), you can track the same by performing some operation while running profiler to track down what is happening.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply