Oh don't remind me! Ha ha ha.

No worries...

My first reaction was, "LOL!". Posted a more serious comment.

Only the compiled plan is held in the plan cache (as G² has shown). The...

Ah, that was just a 'joke' comment about the reason behind the parsing behaviour.

How's the refusing to be baited by Celko thing going, Lynn?

CELKO (9/14/2012)

---

By definition it cannot be a key; it is not an attribute of any entity in the logical data model. A well-designed key should have validation rules (a regular...

capnhector (9/14/2012)

---

i could see this going away in the next version of Sql Server (version after 2012). Reason being *= and =* no longer work as of 2008 (Unless...

Yes. AFAIK, the 'yyyymmdd' format is always OK. I personally try to use a CONVERT with an...

GSquared (9/14/2012)

---

Or...

GSquared (9/14/2012)

---

Or "by design because they hoped it would never come up and couldn't figure out a good solution for it". I've seen that one before too. (As...

Gazareth (9/14/2012)

---

SQL Kiwi (9/14/2012)

---

The comma form parses correctly if you list Worker second:

Select M.name, F.name, B.name

From Role F, Worker M

LEFT JOIN Worker B ON M.superiour=B.nr

Where M.Role = code

It might be...

ChrisM@Work (9/14/2012)

---

[font="Courier New"]

Table Ind_level External Fragm(%) Avg Frag Size Page_count Internal Fragm(%) Ind_size (KB)

identity ...

Jeff Moden (9/12/2012)

---

SQL Server now uses Type 4 GUIDs which are nothing more than pseudo-random numbers and there's no guarantee that two machines can't generate the same number. The...

IgorMi (9/13/2012)

---

The above from BOL has proved true in a test i did some weeks ago. I wanted to see the fragmentation, page counts, index sizes for int, bigint, newid()...