With 3 correct choices out of 4, I'd phrase it "Which statement would NOT run correctly" and dispense with multiple choices. /nitpick

An easy question. I always use AS when I...

Well, the question was which...

Well, if ALL you want is the two counts, why not do this?

select

Count1 = (select COUNT(*) from #Table1),

Count2 = (select COUNT(*) from #Table2)

Well, the good news is, I got NULLs down pat. The less good news is, I didn't even stop to think about type precedence.

Conclusion - time for more coffee.

Nice easy question, with a bonus discussion about one-row tables.

On the second thought, the table in the question allows 0 or 1 rows, while Hugo's example ensures that the...

Nice and easy afternoon question, here.

Right, poster #627 to complain about the wording. With the little twist that I stared at it, thought I spotted the gotcha and said, "Aha! The batch returns an error,...

The benefit of replying a few days later and fully caffeinated.

Even so, I almost missed the INSERT ... SELECT part. :hehe:

Fun question, and yes, a helpful technique for populating...

Narud (9/6/2012)

---

Hugo Kornelis (9/6/2012)

---

I'd put it differently. The only difference between...

+1

g_one_2020

---

As per the post, NULL may be NOT EQUAL to 2, so we should get...

Well, sheesh, way to make it simple! I was having such fun with my pivots!

Thanks, Luis.

I was wondering the same thing.

BOL says:

Specifies the error response when an insert operation...

The question was quick and easy. It's the last line in the explanation, about alias column names in WHERE that made me go, "Oh!" One of those things I knew,...

I spotted the gotcha, and got it right. I do think it would have been a more educational question if it focused just on the date and time element, without...

Carlo - absolutely that is confusing. When I intend to alias the column, I prefer to use [ColumnName] = col1 syntax, which aligns all my column names nicely.

The problem...