Peter Brinkhaus (1/6/2012)

---

Performance with 256MB is tragic anyway, but I've turned the trace on, ran it three times and all runs succeeded.

Peter Brinkhaus (1/6/2012)

---

Using 256MB memory it failed 7 out of 8 times. Ran it once with 512MB, failed also. Ran it once with 1GB, succesfully.

APPLY is named after the process of applying a set of input rows to a table-valued function.

ChrisM@home (1/6/2012)

---

64 bit Vista Home Premium here Paul, but I'll go for it if you give the nod.

J Livingston SQL (1/6/2012)

---

As I have already said...I haven't had any issues before now...and this occurrence ONLY materialized on a memory compromised PC....it has never occurred on our servers.

Jeff Moden (1/5/2012)

---

SQL Kiwi (1/5/2012)

---

Jack Corbett (1/5/2012)

---

Have had a discussion with Aaron Bertrand about case-sensitivity recently.

You knows he's super-anti-underscores?

Makes two of us.

Jack Corbett (1/5/2012)

---

Have had a discussion with Aaron Bertrand about case-sensitivity recently.

L' Eomot Inversé (1/5/2012)

---

As far as I know there is no Connect bug report, and I don't think there's much point in raising one as it's clearly "by design"

SQL Kiwi (1/5/2012)

---

I need to look at it a bit more closely to understand fully what the script is telling me

SQL Kiwi (1/4/2012)

---

As far as I recall, the issue with multiplying or dividing by one was a bug in type inference, which has since been fixed.