May 1, 2013 at 8:33 pm
Comments posted to this topic are about the item Table Alias
Thanks
Vinay Kumar
-----------------------------------------------------------------
Keep Learning - Keep Growing !!!
May 1, 2013 at 8:34 pm
May 1, 2013 at 10:31 pm
Easy Question
Malleswarareddy
I.T.Analyst
MCITP(70-451)
May 1, 2013 at 10:31 pm
May 1, 2013 at 10:31 pm
May 1, 2013 at 11:47 pm
Good basic question Vinay 🙂
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
May 2, 2013 at 12:13 am
YES; finally my powers are restored in my finnnngers (i mean i selected the right answer :-P)
thank you for the post, nothing can beat the classics;
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
May 2, 2013 at 1:17 am
I like explanation!
😀
May 2, 2013 at 1:24 am
Good question, though I'm surprised that, apparently, people are doing this wrong. Since you'll be rewarded by an error message when you try, I don't understand how people could not do this correct - at least after being hit once.
However, to do some nitpicking:
1. If I were to try this code on my system, I would get five errors. All system table (*) names are completely lowercase, so everyone who has a server set up with a case sensitive collation will get error messages. (And I think every development server SHOULD be set up with case sensitive collation - developing there and deploying to a case insensitive server is okay, the other word around is a disaster)
2. I don't see the advantage of using a system table (*) in this question. Why not add a CREATE TABLE to make a simple demo table and use that? Okay, it would have been a bit more code in the question, but it would save all the readers of having to look up if the various columns used in the question actaully exist in sysobjects.
3. And if you must use a system table (*), at least avoid using the deprecated ones. You could have used sys.objects instead. Please don't encourage people to use compatibility views; they might just be gone in the next release!
(*) Yeah, I know, I know. Not system tables, but system views. Or rather: compatibility view (for sysobjects) and object catalog view (for sys.objects)
May 2, 2013 at 1:24 am
EDIT: Double post removed.
(I got an error message when posting, so I assumed the post didn't go through. Should have checked before reposting)
May 2, 2013 at 1:33 am
Hugo Kornelis (5/2/2013)
Good question, though I'm surprised that, apparently, people are doing this wrong. Since you'll be rewarded by an error message when you try, I don't understand how people could not do this correct - at least after being hit once.
Hugo, that's the reason i have post the Question.
And thanks for your suggestions, i will keep them in mind for future questions. 🙂
Thanks
Vinay Kumar
-----------------------------------------------------------------
Keep Learning - Keep Growing !!!
May 2, 2013 at 1:50 am
Nice easy one (even for me!). Thanks.
email: info@weekendwebdesign.co.uk
Personal Website: http://markallen.co.uk/
Business Website: https://www.weekendwebdesign.co.uk
May 2, 2013 at 2:54 am
Hugo Kornelis (5/2/2013)
Good question, though I'm surprised that, apparently, people are doing this wrong. Since you'll be rewarded by an error message when you try, I don't understand how people could not do this correct - at least after being hit once.However, to do some nitpicking:
1. If I were to try this code on my system, I would get five errors. All system table (*) names are completely lowercase, so everyone who has a server set up with a case sensitive collation will get error messages. (And I think every development server SHOULD be set up with case sensitive collation - developing there and deploying to a case insensitive server is okay, the other word around is a disaster)
2. I don't see the advantage of using a system table (*) in this question. Why not add a CREATE TABLE to make a simple demo table and use that? Okay, it would have been a bit more code in the question, but it would save all the readers of having to look up if the various columns used in the question actaully exist in sysobjects.
3. And if you must use a system table (*), at least avoid using the deprecated ones. You could have used sys.objects instead. Please don't encourage people to use compatibility views; they might just be gone in the next release!
(*) Yeah, I know, I know. Not system tables, but system views. Or rather: compatibility view (for sysobjects) and object catalog view (for sys.objects)
+1 🙂
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
May 2, 2013 at 3:37 am
Thanks for the question.
May 2, 2013 at 5:46 am
Thanks for the question Vinay.
An easy one for the day. It's always good to refresh our basics 🙂
~ Lokesh Vij
Link to my Blog Post --> www.SQLPathy.com[/url]
Follow me @Twitter
Viewing 15 posts - 1 through 15 (of 32 total)
You must be logged in to reply to this topic. Login to reply