Query finished, ran 9 minutes 14 secods and returned 7203 rows. Some of the estimated rows are quite high, 9 B for one of them.

I have uploaded my actual...

Chris, Nevermind. I found your post above.

The second query, even with OPTION (MAXDOP 1), is pegging my Dual Proc Quad Core system.

The first query ran extremely fast. I...

Christopher Stobbs (4/15/2009)

---

mmm I'm going crazy here...

Ok with the following query I can confirm that on 200 it takes milliseconds and in 2005 it takes well over 5 minutes and...

Not really sure what "quite...

Here is some code for you to examine and play with. I hope it helps.

declare @StartDate datetime,

@EndDate datetime;

select

...

You indicate an end date in your original post, but I don't see that in your test data. How is this determined or is it passes as a parameter?

Your...

This may be counter-intuitive. on SQL Server 2005, add this to the end of your query: OPTION (MAXDOP 1)

I would still like you to try my other SQL Server 2005...

Take...

Using just the first 2 or 3 values in your test data, could you please provide us with the expected output from the process? This will greatly assist in...

Rowan (4/15/2009)

---

Its a Windows Server 2003 server SP2

Microsoft SQL Server 2005 -...

If you were to execute the procedure I posted above in SSMS, this is how you would do it:

declare @id int,

@uname varchar(50),

...

This is how I would write the procedure:

alter procedure [dbo].[checkComms]

@CommID int,

@username varchar(50),

@status varchar(200) OUTPUT

as

begin

...

Can you tell me more about the configuration of the server all of this is running on?

Had an idea for SQL Server 2005. This WON"T work on SQL Server 2000. Please give it a try, and let's see what happens.

select

*

from

...

While you are capturing the Execution Plan, could you post the complete query code you are running and the DDL (Including indexes) for the two tables.

From what I can tell,...