September 21, 2014 at 12:35 am
Eazy mozo 🙂
Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant
September 21, 2014 at 10:06 pm
Good one..
Vimal LohaniSQL DBA | MCP (70-461,70-462)==============================The greatest barrier to success is the fear of failure ** Success is a journey not a destination**Think before you print, SAVE TREES, Protect Mother Nature
September 22, 2014 at 12:49 am
Nice question thanks.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 22, 2014 at 3:26 am
Thank you for the post, good one. (guessed the answer right also the explanation behind it)
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
September 22, 2014 at 5:08 am
Nice simple one for the start of the week.
Tom
September 22, 2014 at 5:40 am
This was removed by the editor as SPAM
September 22, 2014 at 5:41 am
Good question.
I anticipate many people will go for the NULL answer.
---------------
Mel. 😎
September 22, 2014 at 5:47 am
SqlMel (9/22/2014)
Good question.I anticipate many people will go for the NULL answer.
Yes they will. The concept is important, though. The presence of the row makes all the difference in the world. One might even argue the presence of rows is the start of learning to count. 😉
September 22, 2014 at 6:15 am
Good question, thanks. I got the right answer for the wrong reason -- the explanation helped!
September 22, 2014 at 7:41 am
Got me! 🙁
September 22, 2014 at 7:51 am
Made my guess, ran the code, got back NULL. Not an empty record set - NULL.
September 22, 2014 at 7:52 am
Nice, simple question - good way to get the brain working after the weekend. Thanks! 🙂
September 22, 2014 at 8:06 am
dfortier (9/22/2014)
Got me! 🙁
Me, too. I'll blame it on a Monday morning brain.
September 22, 2014 at 8:09 am
JustMarie (9/22/2014)
Made my guess, ran the code, got back NULL. Not an empty record set - NULL.
So, did I. Even though that's what I answered, that's not what I was expecting since the explanation made sense to me.
Can anyone explain why I would get something back?
Running 2008 R2.
Never mind. I see why. There are two select statements. The second one is doing a select on the variable @test-2 which is null. That's the one that is returning a null value.
Viewing 15 posts - 1 through 15 (of 32 total)
You must be logged in to reply to this topic. Login to reply