Actually this is much simpler :

select productid

from dbo.product_cities

where city in ('boston', 'chicago', 'denver')

GROUP by productid

having count(*) = 3 --number of cities in the in clause.

Select name, A, B, C, D, (A + B + C + D) / 4.0 as Average from dbo.YourTable

Would be nice if we could lock out the admins sometimes .

Typo this time . Corrected now.

I can't test from here... reply to this message so I won't forget to answer this one tomorrow.

dito .

It's the first time I see you hold something in. Don't worry for me, I've been burned before. .

There was a leak a few months/years back. The code was a 600+ mb ZIPPED file. That accounted for only 2% of the source code (win 2K).

It may...

Not a chance... unless someone here thinks otherwise .

Still, with a few hundred billions lines of codes, running a few thousands of possible install combinaisons or software/versions, you're gonna miss a bug. There's no way they can come...

Just a quick question... In what situation would you want to know that information (exists but doesn't wanna say, or we kow it doesn't exists). Why not just go,...

I would assume that OrderID is part of the primary and therefore included in the index. So a simple index on the OrderDate would be enough.

Can you imagine how much testing is required just to have that little bugs??? I wouldn't wanna have to manage all that work...

How is this variable declared?

Ya but it kills the performance of the index seeks... maybe it's time to test SP4 in developement and see if it breaks anything else before applying it.