Home/ Questions/Q 1042383
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T15:30:01+00:00

We just upgraded our SQL Server 2005 to SQL server 2008 R2 and noticed

  • 0

We just upgraded our SQL Server 2005 to SQL server 2008 R2 and noticed some performance problems.
The query below was already slow but now in 2008 it just times out. We rebuild the catalog to make sure its freshly made on 2008

DECLARE @FREETEXT varchar(255) = ‘TEN-T’

select  Distinct ...
from
    DOSSIER_VERSION 
    inner join
    DOSSIER_VERSION_LOCALISED ...
where

    CONTAINS(DOSSIER_VERSION.*,@FREETEXT) 
or 
    CONTAINS(DOSSIER_VERSION_LOCALISED.*,@FREETEXT)

The query takes minutes if you have both conditions enabled.

If you just put the following in the where

CONTAINS(DOSSIER_VERSION.*,@FREETEXT)

Its super fast. Same goes for the case if its just

CONTAINS(DOSSIER_VERSION_LOCALISED.*,@FREETEXT)

Since we are or’ing the results I would expect the time for this query to run to be less than the sum but as stated above it takes minutes/times out.

Can anyone tell me what is going on here? If I use a union (which is conceptually the same as the or) the performance problem is gone but I would like to know what issue I am running into here since I want to avoid rewriting queries.

Regards, Tom

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    See my answers to these very similar questions:

    The basic idea is that using LEFT JOINs to CONTAINSTABLE (or FREETEXTTABLE) performs significantly better than having multiple CONTAINS (or FREETEXT) ORed together in the WHERE clause.

    • 0