For SQL server and access 600 records is insignificant.

That being said you have staff that needs to quickly find the correct one.

Same for employees and worked hours.

I think you need...

HTH, all I did use use the script and like it. Michelle actually wrote it! 😉

Not that I know of, but since I never performed that upgrade that doesn't mean much.

That being said if the query was running fine on SSRS 2K5 + SQL 2K5...

Mad bad, fixed the original url

No point in reinventing the wheel.

Edited http://sqlfool.com/2010/04/index-defrag-script-v4-1

Not sure what you mean by that.

You can prove to yourself that it works by installing 2008 R2 trial locally...

Jack Corbett (10/19/2011)

---

I have to disagree Remi. Full Text would probably work, but doing the parse Peter mentioned at the end of his original post would probably be faster...

Don't know either... Hard to say without seeing some of the data.

As if that ever worked before :-D.

Charles Kincaid (10/19/2011)

---

I have a client on R2 so:

Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation...

Cool, TX.

Oh wait, still on that darn CS server :hehe:.

Scan is a scan here. The index choice won't change and the '%whatever%' won't allow for a seek in any way.

As I said before the only possible way out...

... I was being vague because I wanted you to test (apps or people could be using SA, even if not a good practice).

It's not the kind of change you...

When did that change?

used to be true in 2K unless the article was wrong.

As I said... different plan.

#1 scans, #2 seeks.