﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2005 / T-SQL (SS2K5)  / Full text indexing of symbols? / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Tue, 21 May 2013 06:56:42 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Full text indexing of symbols?</title><link>http://www.sqlservercentral.com/Forums/Topic659919-338-1.aspx</link><description>As you've noticed, some characters are ignored when building the full-text index (e.g. punctuation marks) and it is not possible to change the behaviour of the indexing engine.With MSSearch using the LIKE operator is the only alternative.If, however, searching for these ignored characters is a business requirement, and LIKE is not a viable option for you, you could look at third-party indexing engines.</description><pubDate>Fri, 06 Mar 2009 05:12:16 GMT</pubDate><dc:creator>Matija Lah</dc:creator></item><item><title>Full text indexing of symbols?</title><link>http://www.sqlservercentral.com/Forums/Topic659919-338-1.aspx</link><description>It's clear from behavior that full text indexing is treating symbols (such as @ and &amp;) as "noise".  Yet I'm not seeing them (other than $ in noise.enu) in the noise files.  MSDN searches and Google searches are being annoyingly unhelpful.So can I make full text searches work on these (in particular "@") or do I need to go with LIKE?(re-posting as I inadvertently posted first in SQL 2000)</description><pubDate>Wed, 18 Feb 2009 15:06:28 GMT</pubDate><dc:creator>Pam Brisjar</dc:creator></item></channel></rss>