Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I had this connection pool problem:
How to solve a connection pool problem between ASP.NET and SQL Server?
And I am now tracing using the SQL profiler, and I found some queries take about 400 duration to finish and return data.
Is that value too much?
Could it cause the previous connection pool problem?
400 means 400 ms, or 0.4 seconds.
Whether that is too long really depends. If this is your front page or other high traffic area, then that’s too much unless this is an intranet site. You may need to rethink how that data can be obtained, or use caching to reduce the number of times you actually have to run the query.
If this is a report, or other more involved page, then 400 ms is not out of line. At best you might want to check if the query can be done a bit faster to improve the overall user experience.
You may also want to run the Tuning Advisor to determine if the queries are only running slow because you don’t have the correct indexes.