Imagine that, you'd think they'd have corrected the e-mail they'd already sent out when they corrected the question...

Although incorrect, the answer does highlight an interesting difference between a virtual machine and a physical machine where it comes to logical CPU usage which I never knew about, so...

I do wonder why the limit is set at that. Is it just an arbitrary number Microsoft plucked from the air, or is there an actual reason for it?

Yeah, I think the answer depends on what the hire date of Employee 2 in the database is, and since we don't know that (the question doesn't specify) then either...

That isn't actually what you *said*, though? You said that a (well written) cursor will never, ever beat a WHILE loop, which implies the WHILE is faster?

A WHILE loop is...

RonKyle (9/6/2016)

---

What could have thrown me was that I though ET was 5 hours off GMT. ET is five hours behind time in England and 6 in central Europe....

Got it wrong--read the examples in the AT TIME ZONE article and noticed they were returning the same time, but a different datetime offset, so assumed the same would happen...

Yeah, I was going to say that ought to be...

Got the wrong answer, but that's because I pretty much clicked at random...I wanted to know the actual answer and my Google-fu failed me in finding it. Odd that functionality...

But it also allows the date component to be up to 9999-12-31, so none of the answers would be correct...

Got it wrong because I didn't realise SQL didn't enforce foreign keys on temp tables, so I learned something. Bit more information would have been nice, though, as said above.

D'oh, I must be blind...completely failed to notice the column in the view was called Qty while the SELECT was querying against OrderQty. :crying:

Terje Hermanseter (6/6/2016)

---

Since we don't have a 2016 server that I could test this on, I tried to read the documentation for clues. Found this article, https://msdn.microsoft.com/en-us/library/dn246937.aspx, but sadly it...

A...