First connection timeout when using full text indexing

After rebooting the computer (anytime), the first call to the database will almost always time out. This did not happen prior to adding the full text index to the database. It will time out even in the SQL Express Management Suite.

After that first time out, it works fine.

We tried a workaround by making our first call to the database a "dummy" call and wrapping it in a try/catch.

That didn't work either. Any suggestions?

Regards,

Pat

Someone suggested that your issue may be described in the KB, check it out here.

Mike

|||

The article you referred to is about querying the database. However, our problem is at connection time. When the appliction try to start a connection to the database after the SQL server machine reboot, it always timeout. We then try to make the connection again and it always works!

First of all, we didn't have this problem before we add Full-Text index to our database. The happens ONLY with SQL Express with the default security setup, which means the SQL Express instance is owned by "Network Services". When we make "Local System" to be the owner of the SQL Express instance, the problem goes away. This problem also NEVER happens on a server running the Full SQL Server version which default to use "Local System".

We could not find a way to default SQL Express to run on "Local System". If anyone knows of a way to do this, it will solve our problem too.

|||

Mike Wachal - MSFT wrote:

Someone suggested that your issue may be described in the KB, check it out here.

Mike

Thank you for your help, I solved my problem with sp_fulltext_service 'verify_signature', 0;