Timeout expired error in QA while login | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Timeout expired error in QA while login

Many times when I supply loginname & pwd to QA to login to db,I recive a timeout error.What should i do to resolve it.This may also give trouble to application.Pls suggest
Ensure server ALIAS is defined in client network utility and check LMHOSTS file, try to ping the server and see responses are acknowledged. You may also check if AUTO_CLOSE is enabled on the default databases, that might contribute in this timeout too. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Also try connecting the server by supplying IP address of server as it gets resolved quickly and quickly traceble in network then alias name.
AUTO_CLOSE is enabled.So I unchecked that.
But I am wondering when I created db by EM,I havent enabled this property.Neither it was enabled in model db.How did it automatically got enabled.Any ideas??
BOL states:By default, this option is set to ON for all databases when using Microsoft® SQL Server™ 2000 Desktop Engine (MSDE 2000), and OFF for all other editions, regardless of operating system. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
I am using Personal Edition and not MSDE
THen you must check from Application side whether it is controlled in that manner.
Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
No third party application or tool is configured to do so.This came as really shocking to me because each time I create a new db using EM and then click the properties–>option tab.I see the AUTO_CLOSE option is enabled.
I guess MS has forgotten to list the fact that personal edition also has AUTO_CLOSE option enabled by default
I don’t have Personal Edition so I cannot reproduce the error and I appreciate you found the issue. You may shoot an email to SQL support for further clarification. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>