asked
Why have phrase matches stopped working in my 2008 instance?
According to [this][1]: > Use of WEIGHT, FORMSOF, wildcards, > NEAR and other syntax is not allowed. > freetext_string is wordbroken, > stemmed, and passed through the > thesaurus. **If freetext_string is > enclosed in double quotation marks, a > phrase match is instead performed**; > stemming and thesaurus are not > performed. Indeed, this has worked just fine for me up until now (mostly on 2005). But on my 2008 instance at home, it's suddenly started ignoring the double quotes in any query I do: SELECT TOP 3 Title FROM Articles WHERE FREETEXT([Title], '"global warming"') Results: China takes Congress-centered stance in prevention of global warming Global Nanotechnology R&D Hub Taking Shape in Tsukuba Warming-related drought leads to decline in plant growth, reversing earlier trend Why is the `FREETEXT` predicate stripping or ignoring the double quotes in my query? I found [this][2] post that seems to suggest this behavior has changed in 2008. Does that mean the MSDN documentation is incorrect? And how can I most easily restore/simulate the previous behavior? [1]:
http://msdn.microsoft.com/en-us/library/ms176078.aspx [2]:
http://social.msdn.microsoft.com/Forums/en-US/sqlsearch/thread/95922ae3-91ad-4524-b1be-6e987656edee
Have a look at this post,
http://social.msdn.microsoft.com/Forums/en-US/transactsql/thread/42409ada-9535-4920-aebf-6e583df689e8 and a link in the above post goes to this link,
http://technet.microsoft.com/en-us/library/ms143709.aspx hope this helps...
Thanks Daniel. Looks like I'm switching to `CONTAINS[TABLE]` then. I had hoped to avoid it because translating a query such as `"global warming" extreme` is harder because I need to change that to `"global warming" AND extreme` otherwise `CONTAINS[TABLE]` can't parse it.
