Initial connection very slow
-
When 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 am guessing 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?
How 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?
Thank you,
Peter
-
Anyone have an idea on this?
-
is your database set to autoclose?
Cheers,
- Mark -
no, i checked that. autoclose is turned off. is there maybe a way to establish a permanent or cached connection between the web server and SQL server or set SQl server up differently?
-
If your webserver and database were on same machine initially, they would have used named pipes for communications, which is a bit faster them TCPIP. try switching to named pipes connection in your web server.
refer to BOL for details on Named Pipes vs. TCPIP
-- Amit
-
no, they are on different machines and use tcp/ip.
-
Do you notice any improvement from specifying port number (1433?) rather than dynaically determining the sql server port?
Cheers,
- Mark
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply