I have an odd situation with a full-text index in SQL Server 2012.
There is a table with 8000 rows. 4 fields are included in a full-text index. At first all worked well, but now there is just this one case when a full-text query times out. The case is when (1) the search is on a single character, e.g. contains (*, 'm*'), and (2) the search is issued by my web site. If I put 2 characters, e.g. contains (*, 'mi*'), the query comes back right away. If I capture the one-character query in SQL Profiler and execute it in query window, the query comes back right away. But, I am pretty sure the timeout is on the query since I can see from Fiddler and SQL Profiler that as soon as the web request gets a 30-second timeout, the SQL Profiler (In tuning mode) shows the one-character query "complete" with 30-second duration.
Recyling the web didn't fix the issue, neither doing a full re-population of the index. I was able to resolve this problem by re-creating the full-index. But, obviously, it's not a sustainable answer going forward. The problem is that I don't know how else I can troubleshoot this issue. If you know what's going on, that would be wonderful -- but, I am also just looking for an advice on how I can troubleshoot this.
Thanks.