Question

We have a page calling a Search stored procedure which internally uses SQL Server 2005 FTS. If the application remains idle for 10-15 mins, the first consequent call to the stored procedure times out. All subsequent calls work.

Is there any way to prevent this from happening? We don’t want the first user getting a timeout and we also don’t want to change our code.

Kind regards,

Answer 1

I had a similar problem, well the fts timeout is similar, the rest is different (I’m not using a stored proc or a web page), not that I think it matters. The very first search query of the day would fail with a timeout error and then subsequent queries would succeed.

I stumbled on this link on reddit today: http://support.microsoft.com/?scid=kb%3Ben-us%3B915850&x=15&y=8.

Basically, if your SQL Server doesn’t have access to the internet you can get a timeout. Running the command (below) found at that link totally solved the problem for me.

sp_fulltext_service ‘verify_signature’, 0;
GO

You’ll want to read the full article before you decide to do this on your server.

Hope this helps.