March 11, 2014 at 9:14 pm
Comments posted to this topic are about the item Schema & Renaming Fun
March 11, 2014 at 11:13 pm
Good Question. Getting +2 questions continuous in a row
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
March 12, 2014 at 12:12 am
Thanks for the question.
You have given a hint in QOD to select one option out of 3.
--CLEANUP:
--use master
--drop database xSchemingFun
--drop login qodschemingfun
The above hint tells that database and login will be created successfully.
March 12, 2014 at 2:01 am
"Schema cannot be named Not" ?????
"It could be said the table is not funny" ????
Bad wording?
March 12, 2014 at 2:23 am
pmadhavapeddi22 (3/12/2014)
Thanks for the question.You have given a hint in QOD to select one option out of 3.
--CLEANUP:
--use master
--drop database xSchemingFun
--drop login qodschemingfun
The above hint tells that database and login will be created successfully.
+ 1
Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant
March 12, 2014 at 3:03 am
Great question, thanks!
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 12, 2014 at 3:09 am
Interesting question, just a shame that it's let down (as QOTDs so often are) by case inconsistencies.
On a case sensitive database you get several errors and end up with a table called "ny".
March 12, 2014 at 6:14 am
Hmmm.
According to BOL 'not.funny' should be treated as a failure:
[ @newname = ] 'new_name'
Is the new name for the specified object. new_name must be a one-part name and must follow the rules for identifiers. newname is sysname, with no default.
Or does it mean, no space allowed in new_name?
March 12, 2014 at 6:53 am
I found this to be fun and funny and not very .not.funny.
I was first screaming about the scheming. After I realized what was up, it brought a smile to my face.
Tom
March 12, 2014 at 7:11 am
palotaiarpad (3/12/2014)
Hmmm.According to BOL 'not.funny' should be treated as a failure:
[ @newname = ] 'new_name'
Is the new name for the specified object. new_name must be a one-part name and must follow the rules for identifiers. newname is sysname, with no default.
Or does it mean, no space allowed in new_name?
'not.funny' is just a name as [not.funny].
March 12, 2014 at 7:31 am
Thanks for the comment on the hint in the cleanup - good catch for you, dumb mistake for me:-)
March 12, 2014 at 7:32 am
I'll try to remember the case sensitivity going forward and add it to my list of things to check.
March 12, 2014 at 7:49 am
Thanks Andy. On a not.funny note, this was a good question.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 12, 2014 at 8:48 am
Well, I thought I knew my reserved words....
March 12, 2014 at 9:11 am
Hah hah hah! Thanks, Andy!
Viewing 15 posts - 1 through 15 (of 22 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy