February 28, 2009 at 6:12 am
Jeff Moden (2/27/2009)
Seems like the only difference between you and me as that I never honor the case of the system objects except for very large auto-generated scripts... even then, if it's going to become production code, I'll go in and clean it all up to match my conventions.
Like Lynn, I've worked in case-sensitive environments before and in those cases, there isn't really a choice.
select * from sys.Objects
Msg 208, Level 16, State 1, Line 1
Invalid object name 'sys.Objects'.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 28, 2009 at 8:25 am
Hey Gail, I'm stuck in an environement like that where it was installed CS. Have you found any advantages of using CS collation?
February 28, 2009 at 8:33 am
GilaMonster (2/28/2009)
Jeff Moden (2/27/2009)
Seems like the only difference between you and me as that I never honor the case of the system objects except for very large auto-generated scripts... even then, if it's going to become production code, I'll go in and clean it all up to match my conventions.Like Lynn, I've worked in case-sensitive environments before and in those cases, there isn't really a choice.
select * from sys.ObjectsMsg 208, Level 16, State 1, Line 1
Invalid object name 'sys.Objects'.
Heh... obviously...
That brings up another question... why would anyone make a whole server case sensitive? I can see it on a column here and there and understand the advantages on certain types of data, but a whole server? What is the advantage to making a whole server case sensitive?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2009 at 12:58 pm
Ninja's_RGR'us (2/28/2009)
Have you found any advantages of using CS collation?
No.
Jeff Moden (2/28/2009)
What is the advantage to making a whole server case sensitive?
In the cases I worked on, it wasn't the entire server (with one exception), just one or more databases on the server (3rd party vendors). The one exception was also a 3rd party app and the entire server was case-sensitive because of collation conflicts with tempDB (It was the easier solution)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 28, 2009 at 2:16 pm
Jeff Moden (2/28/2009)
GilaMonster (2/28/2009)
Jeff Moden (2/27/2009)
Seems like the only difference between you and me as that I never honor the case of the system objects except for very large auto-generated scripts... even then, if it's going to become production code, I'll go in and clean it all up to match my conventions.Like Lynn, I've worked in case-sensitive environments before and in those cases, there isn't really a choice.
select * from sys.ObjectsMsg 208, Level 16, State 1, Line 1
Invalid object name 'sys.Objects'.
Heh... obviously...
That brings up another question... why would anyone make a whole server case sensitive? I can see it on a column here and there and understand the advantages on certain types of data, but a whole server? What is the advantage to making a whole server case sensitive?
I once heard that dbas have a penchant for being meticulous... hey, that's two consonants away from rediculous! :w00t:
Max
February 28, 2009 at 2:22 pm
Jeff Moden (2/27/2009)
Max (2/27/2009)
GilaMonster (2/27/2009)
Max (2/27/2009)
Always wondered of there was an overhead with using equal aliases though.No, but it is deprecated syntax
Pity, it's grown on me and quite like it, somehow it's quite readable. Always used
ASwhich is a whole extra character.I really, really like the ...
SELECT alias = ColumnOrExpression
... syntax because of two things... 1st, it makes it really easy to write test code for an update... when you're done, just change the SELECT to a SET and and the UPDATE above that.
2nd, since "expression" can vary widely in length, the use of "AS" ends up as pretty much a ragged right adventure in trying to find column aliases. When the column aliases to the left and the fact that they're pretty much all the same length in a query, it makes readability a whole lot easier.
Yip, somehow:
SELECT ColumnA AS AliasA,
ThisIsColumnB AS AliasB,
DidIMentionThisWasColumnC AS AliasC...
just doesn't do it for me. 🙁
Max
March 2, 2009 at 7:30 am
*snigger*
http://www.sqlservercentral.com/Forums/Topic666430-146-1.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 2, 2009 at 7:37 am
GilaMonster (3/2/2009)
*snigger*http://www.sqlservercentral.com/Forums/Topic666430-146-1.aspx
WOW, he got the hint!!!
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
March 2, 2009 at 7:43 am
That was a pretty good answer from you Gail...:hehe:
And he got the hint. Look up BOL...:hehe:
-Roy
March 2, 2009 at 7:56 am
Alvin Ramard (3/2/2009)
GilaMonster (3/2/2009)
*snigger*http://www.sqlservercentral.com/Forums/Topic666430-146-1.aspx
WOW, he got the hint!!!
It wasn't exactly subtle.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 2, 2009 at 8:35 am
GilaMonster (3/2/2009)
Alvin Ramard (3/2/2009)
GilaMonster (3/2/2009)
*snigger*http://www.sqlservercentral.com/Forums/Topic666430-146-1.aspx
WOW, he got the hint!!!
It wasn't exactly subtle.
Great statement I ran into somewhere, "That man's as subtle as a two-by-four upside the head."
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
March 2, 2009 at 1:04 pm
Jeff and Gail:
http://www.sqlservercentral.com/Forums/Topic666052-338-1.aspx
Is this "feed a fish", "teach to fish", or ask "Why on earth do you want fish?" I'm waiting to see if the OP comes back with a response to your questions. Rather than justify himself to you, he may have just taken the first solution offered and run with it.... and the solutions offered were sub-optimal. Rather than just asking why and demanding to know the business reasons behind a request, you might try leading with a warning about why it's a bad idea to even try to do it that way.
Reading the initial post, I'm not even sure that the OP was talking about creating a permanent table. But Jeff, please note I did not just jump right in with the FOR XML solution. 😉
__________________________________________________
Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills
March 2, 2009 at 1:24 pm
Bob Hovious (3/2/2009)
Is this "feed a fish", "teach to fish", or ask "Why on earth do you want fish?"
"Why are you trying to fish with a shovel?"
I used to get this a lot from my devs at my last company (at least initially). They'd come to me with weird and far-out questions. The first couple times I just answered them. Then I asked one of them why they wanted to know. It turned out that they were trying to solve database problems with insufficient knowledge, coming up with very strange ideas and then coming to me with questions on implementation. When I persuaded one of the guys to explain the initial problem to me, it turned out there was a trivial solution that the devs didn't know about at all.
I'm not saying that the OP there is wrong, or doing something stupid or anything like that. I want to know the reason behind this as it's possible that there's a completely different way of doing whatever it is.
Or, as I used to tell my devs, "Bring me the original problem, not half a solution"
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 2, 2009 at 1:29 pm
Always ask what they want to do. They often don't know the problem.
March 2, 2009 at 1:32 pm
1) http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=120736
2) http://www.sqlservercentral.com/Forums/Topic666657-266-1.aspx
Why do people have no backups, no regular backups, no offsite backups, etc, etc.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 15 posts - 2,116 through 2,130 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply