Re: Code in the database or middle tier (the CLR controversy)

JRStern (jxstern_at_bogus.com) writes:
> Don't know what this has to do with CLR controversy, but ...
>
> If indeed those six alternatives are equivalent, then #4 is certainly
> the best one to give any competent RDBMS.

I will have to agree with Daniel that #6 is my favourite. I will have to say that I did not at all expect #4 to have the same plan as #2 and #6 (which I suspected would have the same plan).

And the reason that #6 is my favourite, is not because of performance, but because it expresses the problem better: "show me all servers that have a server instance"). (#2 does this as well, but is less extensible, as it breaks down for two-column keys, unless you have set constructors, which SQL Server has not.)  

> Except that you might try learning ANSI join syntax.

[Quoted] Here I don't agree with Daniel, and I will have to say that I was surprised to see his dismay for this syntax. Then again, it took me some time to start appreciate it. But it might be that Oracle's proprietary operator for outer join (+= or whatever it is) is less horrible than SQL Server's old *=.

-- 
Erland Sommarskog, SQL Server MVP, esquel_at_sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp