Comments for SQL Server Full-Text Search (FTS) Bloghttps://blogs.msdn.microsoft.com/sqlfts
Official blog managed by the SQL Server Full-Text Search engineering team
Sun, 30 Mar 2014 18:41:25 +0000hourly1Comment on Creating Custom Dictionaries for special terms to be indexed ‘as-is’ in SQL Server 2008 Full-Text Indexes by Philhttps://blogs.msdn.microsoft.com/sqlfts/2009/12/03/creating-custom-dictionaries-for-special-terms-to-be-indexed-as-is-in-sql-server-2008-full-text-indexes/#comment-194
Sun, 30 Mar 2014 18:41:25 +0000https://blogs.msdn.microsoft.com/sqlfts/2009/12/03/creating-custom-dictionaries-for-special-terms-to-be-indexed-as-is-in-sql-server-2008-full-text-indexes/#comment-194Please disregard my comments above about the use of the # character and the filename of the custom dictionary on SQL Server 2008. Further investigation has determined that those findings are not correct.
]]>Comment on Creating Custom Dictionaries for special terms to be indexed ‘as-is’ in SQL Server 2008 Full-Text Indexes by Philhttps://blogs.msdn.microsoft.com/sqlfts/2009/12/03/creating-custom-dictionaries-for-special-terms-to-be-indexed-as-is-in-sql-server-2008-full-text-indexes/#comment-183
Fri, 28 Mar 2014 03:15:55 +0000https://blogs.msdn.microsoft.com/sqlfts/2009/12/03/creating-custom-dictionaries-for-special-terms-to-be-indexed-as-is-in-sql-server-2008-full-text-indexes/#comment-183On SS 2012 the filename for an English dictionary looks like it needs to be Custom0009.lex. On SS 2008 it needs to be Custom1033.lex.

Also the # symbol seems to work as a wildcard for numbers on 2008, but not on 2012.

It would be REALLY nice if this was all documented somewhere.

]]>Comment on Creating Custom Dictionaries for special terms to be indexed ‘as-is’ in SQL Server 2008 Full-Text Indexes by Philhttps://blogs.msdn.microsoft.com/sqlfts/2009/12/03/creating-custom-dictionaries-for-special-terms-to-be-indexed-as-is-in-sql-server-2008-full-text-indexes/#comment-173
Fri, 28 Mar 2014 03:13:07 +0000https://blogs.msdn.microsoft.com/sqlfts/2009/12/03/creating-custom-dictionaries-for-special-terms-to-be-indexed-as-is-in-sql-server-2008-full-text-indexes/#comment-173Mark, did you rebuild your full-text index?
]]>Comment on Looping over document similarity details in Semantic Search by Umamaheswari.Rhttps://blogs.msdn.microsoft.com/sqlfts/2011/10/31/looping-over-document-similarity-details-in-semantic-search/#comment-163
Fri, 29 Nov 2013 00:49:57 +0000https://blogs.msdn.microsoft.com/sqlfts/2011/10/31/looping-over-document-similarity-details-in-semantic-search/#comment-163How do you calculate semantic key phrase score
]]>Comment on Creating Custom Dictionaries for special terms to be indexed ‘as-is’ in SQL Server 2008 Full-Text Indexes by Markhttps://blogs.msdn.microsoft.com/sqlfts/2009/12/03/creating-custom-dictionaries-for-special-terms-to-be-indexed-as-is-in-sql-server-2008-full-text-indexes/#comment-153
Mon, 14 Oct 2013 09:25:18 +0000https://blogs.msdn.microsoft.com/sqlfts/2009/12/03/creating-custom-dictionaries-for-special-terms-to-be-indexed-as-is-in-sql-server-2008-full-text-indexes/#comment-153Has anyone had any success with these instructions? I found them about 18 months ago and after much fiddling managed to get some simple phrases picked up by the search, from my custom dictionary.

However I'm now trying to amend my already working dictionary to include some new phrases and cannot get it to work. The command exec sp_fulltext_service 'restart_all_fdhosts simply doesn't get the search to pick up the custom dictionary again.

The old entries still work, the new ones are not picked up. I feel like there's something else I need to restart somewhere. We've stopped and started the SQL instance, I've even in desperation deleted my index completely and rebuilt it from scratch, but no effect.

I have found several thread on the internet of people having similar problems but none have a resolution.

I'm curious to know, do the 4 "oppgj" in the DMV output table in Scenario 2 show up coincidentally because they turn out to be proper Swedish words, or did the word breaker somehow chop off the "ØR" part in OPPGJØR ?

The latter would pretty much explain my problem, but I'm still unsure if I'm experiencing the same bug explained in KB 973090 ("the query may return incorrect data" is rather vague…)

]]>Comment on Looping over document similarity details in Semantic Search by SEMANTICKEYPHRASETABLE is super slow to mehttps://blogs.msdn.microsoft.com/sqlfts/2011/10/31/looping-over-document-similarity-details-in-semantic-search/#comment-123
Fri, 09 Mar 2012 15:02:21 +0000https://blogs.msdn.microsoft.com/sqlfts/2011/10/31/looping-over-document-similarity-details-in-semantic-search/#comment-123I have a table (NOT a FileTable) containing 2.5M records with a field containing content of plain text. I created a Fulltext index on it with semantic option. The fulltext catalog is on a separate filegroup and file. It is now 4GB big. The index is auto track changes and populating. Then I did the following search