ammon.poage (5/13/2013)
First time poster here. I got it wrong, which is fine. When I answer a question, I try to answer without running the code. Sometimes I try to research BOL or ask a teammate, but when I read from the comments of 'You got it WRONG' and it specifies that the question is about buggy behavior instead of expected outcomes - specifically opposite of what's written in specs, it crosses a strange boundary for me. When the data shows you Correct answers: 27% (207)Incorrect answers: 73% (565)
the crowd is guessing at best or answering like I did without running the code but running to BOL to check. I guess the 'rules' don't specify 'don't run the code'. I guess I should change my strategy to just run the code and watch what happens. Thanks for the question, but I don't think it was a good one.
/rant = off.
Thanks for exposing inconsistent behavior of Sql Server.
These are the questions I find most valuable. Since this behavior is not expected or reflected in the documentation, the only other way to discover it is through experience... I'd much rather learn about it beforehand!