Ed Wagner (11/25/2013)

---

Revenant (11/25/2013)

---

L' Eomot Inversé (11/25/2013)

---

crookj (11/25/2013)

---

Kurt W. Zimmerman (11/25/2013)

---

Ed Wagner (11/25/2013)

---

High...

Glad to see I'm not the only pedant in the pool. 🙂

But...

Old Money

Yes, that's important.

[

Nothing spells a good day at work like reviewing a query containing multiple nested table expressions; all the while, no indentations -...

Robert Davis (11/24/2013)

---

If you're going to store it as MMYYYY, I would store it as an int, not a date or datetime. Otherwise, it will be converted to a different...

There are a few failings that I find irritating:-

The inability to represent domain constraints directly. If I have some domain that is used in many coulumns and in many...

Jeff has already explained it, but I can't resist providing you with this link[/url].

I would keep it as date (not datetime).

Then add a table constraint as suggested by Luis and fix the day part of the date either by an instead...

Nice question.

But 27% wrong answers! (242 out of 520). That's pretty amazing. Nearly half the people who replied don't know that security princials are listed in the sys.server_principals DMV...

I think the idea of "Core TSQL" isn't unreasonable, but no set of knowlege which is just about T-SQL and not about the bigger picture will ever make a competent...

Jeff Moden (11/22/2013)

---

From the article:

---

This week I'm curious if we can debate about, and compile, a list of core skills with T-SQL that we think someone ought to understand to...

That seems the hard way to do

update table1 set field1 = 0 - field1;

(or even...

The problem with the original join, according to the table definitions given, is that the field in the enrollment table is called epatientid, not patientid. So naturally the name...

spices

Yes, I'm probably being...