Full Text Search intermittently produce inconsistent results

  • We have been using Full Text Search (FTS) for our online search with pretty good results. However once in a while, FTS return very few results (0 or 1) and I have not been able to figure out what caused it. Performing the exact same search soon after would work properly with 100+ results.

    I've been getting complains and it got escalated, so I have to figure out the reason and see if I can avoid this from happening.

    I wonder if anyone have encountered similar problems? All this while, I suspect this happened when the catalog is getting updated when the search is performed. Since it happens so intermittently, detecting this problem is very hard. I hope this can be solved outside of a Microsoft FTS patch. I would like to hear if someone else have experienced similar problem, thanks very much in advance.

  • I've had zero problems.

    If you post the query you're using it's possible someone would be able to see where something is amiss.

    └> bt



    Forum Etiquette: How to post data/code on a forum to get the best help[/url]

  • The main search query is straight forward, here's the simplified version of it:

    SELECT * FROM CONTAINSTABLE(dbo.SearchTable, (Col1, Col2), '(FORMSOF(THESAURUS,"keyword"))', 1000) AS FT

    INNER JOIN dbo.IndexedViews IV (NOEXPAND) ON IV.ID = FT.[Key]

    As described we are experiencing this problem intermittently where the same exact query will yield very little results (usually with 0 or 1 result), running the same query minutes after the reported problem would work just fine (returning more results). The catalog is set to update automatically for this table.

    This hiccup happens intermittently, so I don't know whether the culprit is with Full Text or the Indexed View (say when either one of them is being updated). I guess I will continue to run test to see if I can replicate the problem. I would really appreciate it if someone else have experienced similar problem and share it here, thanks so much!

    EDIT: After some thoughts, I am pretty sure it's a problem with Full Text not Indexed View. I'm sure Indexed View complies with A.C.I.D. thus it will not cause the problem I've experienced. So it has to be Full Text, I'll just to continue testing to see if I can catch it by any chance. Again if anyone knows anything about this issue, would appreciate the info. Thanks.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply