<p>We're using SQL Server 2005 in a project. The users of the system have the ability to search some objects by using 'keywords'. The way we implement this is by creating a full-text catalog for the significant columns in each table that may contain these 'keywords' and then using CONTAINS to search for the keywords the user inputs in the search box in that index. </p>

<p>So, for example, let say you have the Movie object, and you want to let the user search for keywords in the title and body of the article, then we'd index both the Title and Plot column, and then do something like:</p>

<pre><code>SELECT * FROM Movies WHERE CONTAINS(Title, keywords) OR CONTAINS(Plot, keywords)
</code></pre>

<p>(It's actually a bit more advanced than that, but nothing terribly complex)</p>

<p>Some users are adding numbers to their search, so for example they want to find 'Terminator 2'. The problem here is that, as far as I know, by default SQL Server won't index short words, thus doing a search like this:</p>

<pre><code>SELECT * FROM Movies WHERE CONTAINS(Title, '"Terminator 2"')
</code></pre>

<p>is actually equivalent to doing this:</p>

<pre><code>SELECT * FROM Movies WHERE CONTAINS(Title, '"Terminator"') &lt;-- notice the missing '2'
</code></pre>

<p>and we are getting a plethora of spurious results.</p>

<p>Is there a way to force SQL Server to index small words? Preferably, I'd rather index only <em>numbers</em> like 1, 2, 21, etc. I don't know where to define the indexing criteria, or even if it's possible to be as specific as that.</p>

<hr>

<p>Well, I did that, removed the "noise-words" from the list, and now the behaviour is a bit different, but still not what you'd expect. </p>

<p>A search won't for "Terminator 2" (I'm just making this up, my employer might not be really happy if I disclose what we are doing... anyway, the terms are a bit different but the principle the same), I don't get <em>anything</em>, but I know there are objects containing the two words.</p>

<p>Maybe I'm doing something wrong? I removed all numbers 1 ... 9 from my noise configuration for ENG, ENU and NEU (neutral), regenerated the indexes, and tried the search.</p>

[{'answer_id': 71604, 'author': 'Darren Gosbell', 'author_id': 11860, 'author_profile': 'https://Stackoverflow.com/users/11860', 'pm_score': 3, 'selected': True, 'text': '<p>These "small words" are considered "noise words" by the full text index. You can customize the list of noise words. This <a href="http://arcanecode.wordpress.com/2008/05/29/creating-and-customizing-noise-words-in-sql-server-2005-full-text-search/" rel="nofollow noreferrer">blog post</a> provides more details. You need to repopulate your full text index when you change the noise words file.</p>\n'}, {'answer_id': 77553, 'author': 'Darren Gosbell', 'author_id': 11860, 'author_profile': 'https://Stackoverflow.com/users/11860', 'pm_score': 0, 'selected': False, 'text': '<p>I knew about the noise words file, but I\'m not why your "Terminator 2" example is still giving you issues. You might want to try asking this on the <a href="http://forums.microsoft.com/Forums/ShowForum.aspx?ForumID=93&amp;SiteID=1" rel="nofollow noreferrer">MSDN Database Engine forum</a> where people that specialize in this sort of thing hang out.</p>\n'}, {'answer_id': 124518, 'author': 'xnagyg', 'author_id': 2622295, 'author_profile': 'https://Stackoverflow.com/users/2622295', 'pm_score': 0, 'selected': False, 'text': '<p>You can combine CONTAINS (or CONTAINSTABLE) with simple where conditions:</p>\n\n<p>SELECT * FROM Movies WHERE CONTAINS(Title, \'"Terminator 2"\') and Title like \'%Terminator 2%\'</p>\n\n<p>While the CONTAINS find all Terminator the where will eliminate \'Terminator 1\'.</p>\n\n<p>Of course the engine is smart enough to start with the CONTAINS not the like condition.</p>\n'}]
['https://Stackoverflow.com/questions/71562', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/2384/']