Good synopsis of uses, Andy!

Sounds to me like Tab1 is nothing more than a subset of Tab2... that would cause such a return even though only an inner join were present.

I can't find any documention to support my thought on this, but don't you need to have "SA"...

1. Pretty sure the answer is "No".

2. I guess I'm not sure what you mean anymore... you can get a result set from a sproc and use it...

Well Jeff, it looks like you've got another comparison between the new 2005 T-SQL options and good 'ol fashioned set based operations. Here's another great reason not to jump right...

You bet... thank all of you folks for the feedback.

1. Yes... you would need to use it in dynamic SQL within the sproc, though.

2. No, but you can from a User Defined Function... (table variable, that is).

I can tell you you'll never get "8" because it has the exact same criteria as "7" which will always qualify first in your case statement. They ARE order...

I'd only be regurgitating what's in Books Online... recommend you lookup "DELETE" in Books Online for a full explanation of SQL Server's proprietary and nasty fast DELETE. You might...

Things like this are normally simple syntax errors... of course, no one can troubleshoot that for you because you didn't post any code 😉

p.s. In English, they are "single quotes"...

SELECT QUOTENAME(3,'''')

Oh, I understand what you want to do... but why do you want to do this to perfectly good data? Why do you need all of 1 person's info...

Now I remember... it's called "Parameter Sniffing" and, apparently, it can crush otherwise effecient code. Lots of good info on the Web about it... Google it...

Of course it's going to take some time... your sproc has four relatively large SELECTS and they ALL must be recompiled even if only one is going to be used...

The...