Coming into this a bit late....

Another (better, I think) way to explain this, is to think of the USING ... ON as a FULL OUTER JOIN. After performing that join,...

sqlcentral-bugmenot (2/26/2013)

---

Archie is correct - the question and its explanation is incorrect. The QotD feature should teach, and teaching to neglect relational principles and rely on implementation details is questionable....

I had almost missed the different time in the returned output, as I was focusing completely on the data type. Caught is just in time!

I do not agree with some...

Thanks! That is what I normally try to achieve here.

As to that previous post ... with hindsight,...

No, I don't find that interesting at all.

I...

If the sequential aspect is important (i.e. FIRST request must go to FIRST available schedule), then I think a cursor will be faster than any of the alternatives. But make...

Koen Verbeeck (2/10/2013)

---

For me the question was more about the fact you can use Integer instead of int. Didn't know that 😀

The question cleverly had no color coding on the...

When picking my answer, I knew I had a 50/50 chance, because my mindreading skills are still not on par with my SQL skills.

There were two options.

1. The author knows...

So how should Steve have made a QotD about the dangers of select * in a...

Good question, Steve!

Here is a link to the most recent version of the relevant Books Online article: http://msdn.microsoft.com/en-us/library/ms187821.aspx. It's the same aas the one in the explantion, but without the...

You could have saved that time. I just checked for which...

Very good question, and an awesome explanation. (Apart from one small type that you probably put in deliberately to prove that you're still human).

Thanks, Tom!

call.copse (2/1/2013)

---

You're not a fan of the old quirky update then? Much as I dislike the obtuseness of it, I like the performance and admire the ingenuity of it. It...

Christian Buettner-167247 (2/1/2013)

---

Lets drive this a little further:

CREATE TABLE dbo.Test(a INT NOT NULL, B INT NOT NULL)

INSERT dbo.Test (a,b) VALUES(1,2)

INSERT dbo.Test (a,b) VALUES(3,4)

GO

DECLARE @a INT = 100

...

I started to reply here, but as the length of my reply grew I realised I probably better...