If it's a 32 way box, maybe the server is using parallelism on the 2nd plan...

what is the cost of the 2nd query compared to the 2 others (pourcentage).

You obviously have different plans but since I don't see the same thing as you do it's gonna be hard for me to help.

Also I'm confirming that ! and !=...

Always the simplest things that trip you up. Probably worked for so long because the parameters were few and short when called... or maybe you just didn't hear about...

Declare @StartD as datetime

Declare @EndD as datetime

Set @StartD = Dateadd(d, datediff(d, 0, GetDate()), 0)

set @EndD = dateadd(d, 1, @StartD)

Select @StartD, @EndD

Select * from dbo.YourTable where DateCol >= @StartD and DateCol...

Order by 1 will not be supported in 2005... better get used to put the real column in there.

I ran your script but all 3 plans were exactly the same.

What version of sql server are you running?

What is the database compatibility level of the database?

Can you post the...

If only that were true...

Insert into b (sho, evi, col1, col2)

Select sho, evi, col1, col2 from dbo.a A where not exits (Select * from dbo.B B where A.sho = B.sho and A.evi = B.evi)

Can you post the code you are using??

Can you post the code you are using to call the sp along with the results?

Yup but it's gonna be even better next year.

RETURN

is the same as RETURN 0

Do you mean that you get 2 results set instead of one?

Or even...

Order by events.date????????

Because without a second column to sort on, the previous order by doesn't mean a lot...

Just to add even more fuel to this post, it would be better to use the bewteen operator for this task as it would use an index seek and not...

This cannot be done that way... You'd have to code the select statement of the cursor in dynamic sql too.

What problem are you trying to solve?