<div>
Is there by any chance you can Case Sensitive collation defined for your database?<br />
May I know what is the collation of your database and the table columns involved.
</div>


<div>
First of all: Can you rephrase your question? How do you search what exactly? What role are playing those &quot;rules&quot;?<br />
<br />
Then: <a href="https://docs.microsoft.com/en-us/sql/relational-databases/search/query-with-full-text-search?view=sql-server-2017" rel="ugc">FULLTEXT queries are case-insensitive</a>.<br />
<br />
Without testing:<br />
<br />
1) The dot after is handled as a word break, the remaining single letter is normally a noise word and removed. This is controlled by the noise settings according to your language. See <a href="https://docs.microsoft.com/en-us/sql/relational-databases/search/configure-and-manage-stopwords-and-stoplists-for-full-text-search?view=sql-server-2017#upgrade-noise-words-from-sql-server-2005" rel="ugc">Configure and Manage Stopwords and Stoplists for Full-Text Search</a>. And as you're running in SQL 2000 mode, take a look at the noise word files in FTDATA.<br />
<br />
2) &quot;and&quot; and &quot;in&quot; are normally stop-words and not part of the index. Thus test without them in your b) case.
</div>


<div>
&gt;&gt; Then: FULLTEXT queries are case-insensitive.<br />
<br />
Yes, ste5an that's correct..<br />
But I doubt that the issue reported by author has something to do with incorrect collation settings or something related to that..
</div>


<div>
Dear @Raja Jegan R, Dear@Ste5an, thanks for your replies.<br />
<br />
@Raja Jegan R: Yes, I forgot to mention the collation. Its <b>SQL_Latin1_General_CP1_CI_<wbr />AS</b> so its case insensitive. &nbsp;My apologies for skipping it earlier. It goes for the table as well. &nbsp;<br />
<br />
@Ste5an: &nbsp;I am making these searches through an in-house customized VB.net application. &nbsp;By &quot;rules&quot; I was trying to refer to the full-text rules by the default nature of it. &nbsp;When the search is made with exact phrase (ref. ex. 1.a) i.e. with a capital P and a Capital K, results are shown but same is not the case when I use small letters.<br />
<br />
It is significant to mention that prior to length changes, the same searches resulted in output. <br />
<br />
PS: In my original question &quot;SearchPhrase&quot; and &quot;SearchString&quot; both refer to column names.<br />
<br />
Regards.
</div>


ankurdk

<div>
Please test directly in SSMS. <br />
<br />
I'm not sure whether in your situation the &quot;old&quot; noise words lists are used or the &quot;newer&quot; stop words. Imho the problem is caused by single letters being noise (stop words) by default.<br />
<br />
And finally: FULLTEXT search is for naturally spoken language.
</div>


<div>
@lcohan thanks for a comprehensive reply. I shall try out the suggestions mentioned by you and then get back; hopefully with a positive reply.<br />
<br />
Thanks again.
</div>


<div>
Dear @Ste5an,<br />
Thanks for your reply. &nbsp;I shall try out things suggested and get back. But, I am still wondering how come things were working prior to length change and everything went haywire by increasing the length despite re-running the full-text time and again ?<br />
<br />
Thanks.
</div>


<div>
&gt;&gt; But, I am still wondering how come things were working prior to length change and everything went haywire by increasing the length despite re-running the full-text time and again ?<br />
<br />
Missed noticing this column length change before..<br />
If this was done, kindly let us know whether you have rebuilt the Full text catalog or not.<br />
if not, then try to do that once to see whether it helps or not.<br />
<br />
or else, try dropping the Full text index and recreate it to see whether it helps out or not.<br />
As ste5an mentioned about the noise words, you can also try to exclude the noise words like &quot;and&quot; and &quot;.&quot; from your search by following the below steps and rebuild the full text catalog once.<br />
<a href="http://www.dbafire.com/2017/11/04/sql-server-full-text-search-problems/" rel="ugc">http://www.dbafire.com/2017/11/04/sql-server-full-text-search-problems/</a>
</div>


<div>
@Icohan ALTER FULLTEXT INDEX on my_table SET STOPLIST=OFF; worked for me! thanks. <br />
@ste5an and @Raja Jegan R thanks for your contributions.
</div>


<div>
<div class="content wysiwyg-content">
Dear All,<br />
Hi. I have a table in SQL Server 2008 database with compatibility level set to &quot;80&quot; (SQL SERVER 2000). This table is a part of a full-text index containing rules only for this table. The full-text index has five columns of the table qualified as &quot;Eligible Columns&quot;. &nbsp;In order to allow the insertion of a lengthy data for one field say &quot;field2&quot; Varchar(3000) , I increased the size to Varchar(3500). After that, I run the full-text index. &nbsp;But the search results are not working properly. &nbsp;<br />
<br />
For example :<br />
<br />
1.a. Contains(SearchPhrase, '&quot;P.&quot; And &quot;K.&quot; And &quot;Mathis&quot;') -- (Camel Case) <b>Fetches results</b> for Camel Cases.<br />
1.b. Contains(SearchPhrase, '&quot;p.&quot; And &quot;k.&quot; And &quot;mathis&quot;') -- (small case) <b>does not fetch result</b><br />
<br />
2.a. where contains(SearchString, '&quot;Institute of advanced study in education&quot;') -- <b>fetches results</b><br />
2.b. where Contains(SearchString, '&quot;Institute&quot; And &quot;of&quot; And &quot;Advanced&quot; And &quot;Study&quot; And &quot;in&quot; And &quot;Education&quot;') -- <b>does not fetch result</b><br />
<br />
Any insights are appreciated.<br />
<br />
Thanks.
</div>
</div>


Dear All,
Hi. I have a table in SQL Server 2008 database with compatibility level set to "80" (SQL SERVER 2000). This table is a part of a full-text index containing rules only for this table. The full-text index has five columns of the table qualified as "Eligible Columns".  In order to allow the insertion of a lengthy data for one field say "field2" Varchar(3000) , I increased the size to Varchar(3500). After that, I run the full-text index.  But the search results are not working properly.  

For example :

1.a. Contains(SearchPhrase, '"P." And "K." And "Mathis"') -- (Camel Case) Fetches results for Camel Cases.
1.b. Contains(SearchPhrase, '"p." And "k." And "mathis"') -- (small case) does not fetch result

2.a. where contains(SearchString, '"Institute of advanced study in education"') -- fetches results
2.b. where Contains(SearchString, '"Institute" And "of" And "Advanced" And "Study" And "in" And "Education"') -- does not fetch result

Any insights are appreciated.

Thanks.

Problem with Full-Text Indexing in SQL Server 2008

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.

Databases

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

SQL (Structured Query Language) is designed to be used in conjunction with relational database products as of a means of working with sets of data. SQL consists of data definition, data manipulation, and procedural elements. Its scope includes data insert, query, update and delete, schema creation and modification, and data access control.