volter_ddun-856145 (12/23/2010)

---

first thing it can't insert null value in to Table1 AND after running that query in sqlserver i didn't get result as mentioned Correct answer.

Correct answer: 7 rows...

da-zero (12/21/2010)

---

I'm confused: the correct answer is the row that is returned "most of the time"?

If yes, then it isn't a good question, as other answers might be possible. If...

ian.grace (12/20/2010)

---

I don't understand how the first transaction could succeed given the attempt to insert the null value into the not-null field "a". Also, why is the last insert...

philip.cullingworth (12/20/2010)

---

But Answer D is

7 rows where column...

The explanation is more terrible than the question: I should read it at...

The date 21 december 2012 depends on the fact that mayan DBA are still...

Old question and repeated many times.

Richard M Karpel (12/16/2010)

---

Now, I read the section highlighted in BOL, and I expected to get the not defined error message, but I would need to look further and see...

It depends on "Regional Settings".

:-D:-D:-D:-D

The QOtD asks for what is the output of a specific script and this generates this error:

Insert Error: Column name or number of supplied values does not match table definition.

and...

Mayan calendar BUG: 12/12/2012 is the end.

:-D:-D:-D

It's best to use the format 'yyyymmdd' because it's indipendent from "regional setting".

I always use this this syntax:

RIGHT('0000000000' + CAST(SomeNumber AS VARCHAR(10)),10)

Because I didn't know that STR() is also used for formatting, I thought it only converts string to number.

This is an old kind of COBOL bug:

using bad datatype to hold integer:

01 IDX PIC 9.

PERFORM LBL VARYING IDX BY 1 UNTIL IDX > 10.

Endless loop

When I realize that a command or option is deprecated, I stop to waste my time to use it.