First it's a scan, 2nd '%myword%' would find a hit for 'OneOfMyWords' where FTS will not find a hit for that word.

Do you have hyper-threading or multiple cpus on the server?

What version/sp do you have?

SET SHOWPLAN_TEXT ON

GO

--query goes here

GO

SET SHOWPLAN_TEXT OFF

GO

then post the results for the fast and slow queries (with clear identifications).

Seems to be network related... but did you see any difference in the execution plans???

> BSOFH:

>

> It's a term I havn't used (or heard, for that matter) in a couple

> years. Mainly back with "the internet" was just used by people who

> actually knew...

Surely but I can't guide in there... someone else surely will.

Dito on the design error, this will be an amazing nightmare when you have 7 years worth of data to union on. You're better off keeping it all in...

You can't index like that on sqlserver... However you can do a covering index on those 2 columns which would speed up the query.

Well now it's time to look into full-text indexing. This is really not something best handled with the like operator.

I don't know how to do that.. good luck with that project.

Yup we're geeks... but at least that's fun .

I never had that not working... Are you sure you ran it in the correct db?

1 - Make sure you restart the server so that it can update itself.

2 - You just lost all support from Microsoft on that server.

3 - Make sure you have...

Why can't you just fire the job from a sp on the server??

That's just a bug from the forum, when a new member answers an editorial and it is its first post (most likely from a new member), it starts a new...