I am trying to understand a behavior of SQL Server in regards to the full text indexing.

If I have the following SQL:

DECLARE @Parameter1 Varchar(60)
DECLARE @Parameter2 Varchar(60)
DECLARE @AddDate DateTime
DECLARE @AddDate2 DateTime
DECLARE @NoClient Integer

SET @Parameter1='"THE REPORT WRITER"'
SET @Parameter2='"THE REPORT WRITER"'
SET @AddDate='2008-12-16 00:00:00'
SET @AddDate2='2010-12-16 23:59:59'
SET @NoClient=5

SELECT Thread.Numero
 FROM Thread (NOLOCK)
  WHERE (Contains (Thread.Notes, @Parameter1) OR Contains (Thread.Title, @Parameter2)) 
  AND Thread.AddDate>=@AddDate AND Thread.AddDate<=@AddDate2 AND Thread.NoClient=@NoClient
   ORDER BY Thread.Numero DESC

This returns messages where "REPORT WRITER" is found and seems to ignore the "THE" in front as if this is a common word.

However, if I search for "PROBLEM EVEN WITH", this will find messages with "PROBLEM EVEN WHEN" as if there is a certain percentage of phonetic ressemblance.

Basically, I do not need anything of that. In both occasions, the exact string should be found exactly in the messages. Thus, if a message is being returned, this would be because the exact string is found as is.

Is this a bug in SQL Server? If not, is this a normal behavior? If yes, is there a setting we can apply in the full text indexing definition to avoid those unexpected situations?