# Why does not SQL Full Text Indexing return results for words having #?

As an example, my question resembles the adhering to making use of SQL Server 2005:

SELECT * FROM Table WHERE FREETEXT(SearchField, 'c#')


I have a complete message index specified to make use of the column SearchField which returns outcomes when making use of:

SELECT * FROM Table WHERE SearchField LIKE '%c#%'


I think # is an unique letter, so just how do I permit FREETEXT to function appropriately for the question over?

0
2019-05-07 01:18:47
Source Share

The # char is indexed as spelling and also consequently overlooked, so it resembles we'll remove the letter C from our word indexing overlook checklists.

Examined it in your area after doing that and also restoring the indexes and also I get outcomes!

Considering making use of a various word breaker language on the indexed column, to make sure that those unique personalities aren't overlooked.

MODIFY : I additionally located this information :

c# is indexed as c (if c is not in your sound word checklist, see extra on sound word checklists later on), yet C# is indexed as C# (in SQL 2005 and also SQL 2000 working on Win2003 no matter if C or c remains in your sound word checklist). It is not just C# that is saved as C#, yet any kind of uppercase adhered to by #. Alternatively, c+npls (and also any kind of various other lower - cased letter adhered to by a+npls) is indexed as c (no matter whether c remains in your sound word checklist).

0
2019-05-08 21:32:20
Source

Quoting a much - reproduced aid web page concerning Indexing Service question language :

To make use of particularly dealt with personalities such as &, |, ^, #, @, \$, (, ), in a question, confine your question in quote marks (").

Regarding I recognize, full text search in MSSQL is additionally done by the Indexing Service, so this could aid.

0
2019-05-08 21:10:06
Source