February 11, 2004 at 4:26 pm
If someone logs on to my website they have to authenticate with a username / password through SQL Server. This is initially very slow (>5 seconds). However subsequent db requests or logins are almost immediate.
I guess my dedicated webserver needs to establish a connection to the SQL server which is initially costly, but then connection pooling kicks in. When I had my website on a shared webserver initial connections were much faster. is that because other poeple's websites on that server and initial connection could have been established earlier or is my new host just slower? Does each website in IIS and each server user have their own connection and pooling?
Can I fix this issue? Can my global.asa have a permanent connection to my website or some script run every minute and connect to the DB? How long is a default timeout to reconnect to a SQl database? Any ideas how I can overcome this costly intitial connection any other way, i.e. changing settings in SQL Server?
Thanks,
Peter
February 12, 2004 at 9:52 am
Hi,
Have you considered DNS / name resolution problems?
Do the database connection settings use an name or an IP address? If it is a name, it maybe having trouble resolving it, and then finally it broadcasts - which is why you get an initial pause.
February 12, 2004 at 11:41 am
Thanks for your help,
no, it's not DNS. I am using an IP and the ping is less than 1ms. Are there any settings in SQL serer I need to adjust, or can I somehow establish a permanent connection between my webserver and SQL Server?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply