Done 🙂

Some more tests showing the bug "in action":

SELECT '0.5' [Expression], CAST(0.5 as varbinary) AS [Binary Representation]

UNION ALL SELECT 'ROUND(0.5,0)', CAST(ROUND(0.5,0) as varbinary)

UNION ALL SELECT '1.0', CAST(1.0 as varbinary)

UNION ALL SELECT...

Paul White NZ (5/4/2010)

---

Hugo Kornelis (5/4/2010)

---

Here is another repro that runs fine on all clients, to demonstrate that SQL Server itself actually does not have any issues with this code:

--...

Thank you Hugo - feels good to get positive feedback from an expert 🙂

cengland0 (5/4/2010)

---

I would not consider this a bad question - I assume that almost noone actually knew the behaviour differences and actual cause of the...

Does not look like it is settings related.

Here is the code executed via each client tool:

SET QUOTED_IDENTIFIER OFF

SET ARITHABORT OFF

SET ANSI_NULL_DFLT_ON OFF

SET ANSI_DEFAULTS OFF

SET ANSI_WARNINGS OFF

SET...

One important observation: This is an error caused within the client tool, not within SQL Server.

Query Analyzer has no issues; SQL Server management Studio does have the issue.

It does not...

Hi Paul,

thanks for your reply. I managed to get it done with your second option, but the first option does not work for me. The screen looks exactly like your...

Paul White NZ (4/30/2010)

---

Christian Buettner-167247 (4/30/2010)

---

Tested it with SSMS and failed ("Select the Backup Sets to restore" shows no entries after selecting the tail backup in "From device:")

...

If anyone could...

Nice QOTD!

Tested it with SSMS and failed ("Select the Backup Sets to restore" shows no entries after selecting the tail backup in "From device:")

Tested it with the "standard" SQL...

This is an interesting question, but with far too many answer options.

Therefore I did not even try to solve it on my own, but used google *shameonme*

If there were 2...

Thanks for your question as well. As you already indicated, it is hardly possible to cover all cases any time. Keep up the good work!

The following setting will cause the error:

SET IMPLICIT_TRANSACTIONS ON

If this is turned on, the create table statement will also be rolled back, causing the error.

Depending on your settings, the error can also be a valid answer:

True, true, but I even don't trust my own stuff occasionally:D