February 12, 2004 at 6:43 am
Not being a web developer I cannot be sure what the issue is. One thing you can check in SQL Server is if the database Auto Close option is on. YOu can see this in Enterprise manager by right-clicking on the DB and selecting properties and going to the options tab or run sp_dboption 'dbname', 'autoclose' in Query Analyzer. Another issue might be that the .Net web page is recompiling at the first run time which will slow it down.
Jack
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 12, 2004 at 11:51 am
Auto-close is not checked. I do not think it is .NET. I have the same page in simple ASP and it is just as slow. And fact is that all of this used to be fast with my last hosting environment, so the code should be OK. Any other settings in SQL Server you can think of?
February 17, 2004 at 11:07 am
Each application may or may not support connection pooling and this is separate from other applications even if the application target the same server and database. Everything in the connection string must be identical for the connection to be pooled. If something is different like a userid, the connection is not pooled. Lots of stuff can be set at the server level that could affect connections - Max concurrent users, query time out, audit level. I believe the default query time out is 600 seconds.
See http://www.sql-server-performance.com/sk_connection_pooling_myths.asp
or http://www.ondotnet.com/pub/a/dotnet/2004/02/09/connpool.html
for more info
Francis
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply