I didn't even notice it said SQl2000/2005 - somehow I always assume that questions will be targetted at the latest release.

I must admit that I ran the script before answering...

I get a pile of errors when I run it - Cannot insert the value NULL into column 'Seq'.

I eventually worked out that this is because I have ANSI_NULL_DFLT_ON set...

How many times do we have to have questions about the default precision of strings before everyone gets them right?!

Once again we learn that you should never rely on default datatype precision, but specify it yourself!

Nils Gustav Stråbø (12/9/2010)

---

to be able to answer it correctly, without cheating, you will have to manually write down how many rows are inserted in each run of the loop...

But hopefully none of them are still using ANSI_NULLS OFF or any other deprecated features?

The first and third answers are definitely correct (the first being a subset of the third), so I went for 'all of the above'. A good question, spoiled slightly by...

I got it wrong, as the last time I tried any DDL within a transaction was 15 years ago in my Oracle days, when such changes could not be rolled...

Excellent question - which I got right due to having been buitten by exactly this problem in the past, and it took ages to track down the cause

Even ignoring the date format problem, what is this question supposed to teach us? Why would anyone want to convert a date to a float?

Don't worry about it, I've lived in England for all 47 years...

I knew what the answer was, and thought that "The maximum Tax Rates across all State/Province IDs" described it well. I supopose I should have read more closely and realised...

I hope one thing that everybody has learned from these questions is that you should never rely on default precision for anything - you will inevitably get it wrong sooner...

Almost certainly

Knew the answer but had a brain fart and clicked the wrong option, oops!

UMG Developer is right about the explanation.