I worked on a project we just about every program had a comment in it which read

// Jim QQQ is a moron

Jim QQQ was a'programmer' whose brother owned the...

39 shots! First game win. Lost in 38 second game. Great job!

Thanks. You are right about using integers for dates. Just got lazy.

david.gugg (12/16/2014)

---

So as it is currently written, is the query actually doing this?:

SELECT s.*

FROM dbo.Stocks s

WHERE s.id IN ( SELECT s.id

...

Oops. Sorry about leaving the dbo in there. That could be the topic of a good QotD. That can be a nasty, hard to find issue.

Short answer, yes, the WHERE clause could be left out. Thanks for pointing that out.

Long answer: It's usually a bug. The idea is that you are trying to link...

I was unhappy with the whole question because I was sure I got the math right. Then I read some of the other comments and realized that ^ means something...

Yes. Looking at the execution plan, it is using the index for both options.

That's the way I am leaning. After reading a bit, it appears that SQL Server engine will try to optimize the order of the items in the 'IN' clause. This...

Wow. That's pretty compact. Thanks for sharing.

I ran both versions against a DB table with about 1.2 million rows.

Without the get days it took 35 seconds.

With Igor's version it took 39 seconds.

With my version it...

CREATE FUNCTION dbo.fnGetMonthDays(@myDate DATETIME) RETURNS INT

AS

BEGIN

return DATEDIFF(d, DATEADD(month, DATEDIFF(month, 0, @mydate) , 0) ,DATEADD(d, -1, DATEADD(m, 1, DATEADD(month, DATEDIFF(month, 0, @mydate) , 0)))) + 1

END

go

select...