Flush the procedure cache, dbcc freeproccache(), and then rerun the queries. I think MANU might have it. You inserted one table from the other. It's indexes are going to be...

I would definitely start with the trace to see which procedures are running long because I'll bet they're the same ones that are causing this problem. There are some great...

Blocking will require more than perfmon & profiler. Do a search in the scripts and you'll find some timed scripts that will gather that data for you.

SQL Server 2008 is...

Since you're already joining to the table, why not use the FREETEXT in the WHERE clause instead of joining the table to itself?

Whoops. I'm a moron.

Get the execution plan and it will tell you exactly what's occurring when. That's what they do.

You're pretty close

Yes, you need to drop the foreign key...

sherlockian21 (5/30/2008)

---

This is the query:

Select *

from

(

select (top 500 row_number() OVER (ORDER BY(rank desc) as resnum, rank, description, table2.col, table3.col, table4.col

from table1 inner...

To determine what the queries are doing your friend needs to look at the execution plans. That will identify where the time is being spent and suggest possible solutions.

Also, I...

So, if I understand this correctly, the plan is to break down a title into it's component words, store each word in seperate table with a link back the title...

OK. Run Profiler. Be sure you have one of your ADO connections on line. You can just use the defaults. Check the connection settings of the ADO connections. I'll be...

So the query would run fine in SSMS, but when run from VB it times out?

If he already has a design that has 1.2 million rows and he's "considering indexing" then he's way behind the eight-ball already. I'd suggest focusing on one thing, clustered indexes....

The first thing that comes to mind... Have you updated the statistics and/or rebuilt the indexes after moving the data from 7 to 2005? It's my understanding that this is...

Everyone else has nailed it. The one other thing you might consider is using NVARCHAR(MAX) if you are potentially storing more than 50 characters. Well, more than 4000 in this...