| 01:03.49 | *** part/#uphpu Utah_Dave (n=boucha@0-2pool130-228.nas28.salt-lake-city1.ut.us.da.qwest.net) |
| 04:17.12 | *** join/#uphpu synic (n=synic@c-67-177-16-249.hsd1.ut.comcast.net) |
| 06:09.52 | diskotec|w | can anyone answer a sql server script question for me? |
| 06:10.56 | *** join/#uphpu RyanE_ (n=ryan@rberick.dsl.xmission.com) |
| 06:13.32 | diskotec|w | RyanE: do you know sql server scripts well enough to answer a question? |
| 06:18.33 | RyanE_ | maybe |
| 06:18.36 | RyanE_ | 'sup? |
| 06:20.28 | diskotec|w | at the beginning of a select statement it lists a handful of [table names].[column names] but there are a few lines that say a letter a.[column name] how in the world does it know which table the letter a is referring to? |
| 06:20.54 | RyanE | usually, when it says that, if you look at the tables that they're retrieving from, they've aliased a table. |
| 06:21.22 | RyanE | i.e. select a.blah, b.blah2 from Accounts a, Baboons b where a.id = b.id; |
| 06:21.35 | RyanE | so table Accounts is aliased to 'a', and Baboons to 'b'. |
| 06:22.16 | diskotec|w | ah ok... not used to that i guess. for some reason i thought a letter had to be declared before using it. |
| 06:22.37 | RyanE | well, it isn't really declaring a variable or anything, just an alias for the table name. |
| 06:22.44 | RyanE | it's mostly used when joining a table to itself. |
| 06:23.03 | diskotec|w | yeah... sorry....it's just the best way I could explain how I was thinking how it worked. |
| 06:23.15 | *** join/#uphpu Utah_Dave (n=boucha@c-24-10-151-252.hsd1.ut.comcast.net) |
| 06:23.17 | RyanE | for example, let's say you have a table, PC (Model, Speed, RAM, etc.) |
| 06:23.37 | RyanE | if you want to show all the PC's that have the same Speed and RAM, you can do: |
| 06:24.23 | RyanE | select a.Model, b.Model, a.Speed, a.RAM from PC a, PC b where a.Speed = b.Speed and a.RAM = b.RAM and a.Model != b.Model and a.Model < b.Model; |
| 06:24.36 | RyanE | which you couldn't do without aliasing. |
| 06:27.23 | *** part/#uphpu Utah_Dave (n=boucha@c-24-10-151-252.hsd1.ut.comcast.net) |
| 06:29.08 | diskotec|w | cool...thanks for the info. I've been running traces using the Profiler to figure out how our software vendor put together some of their reports. |
| 06:29.54 | RyanE | no problem. I had an old friend call me from Ohio tonight to ask me an SQL question, and it happened to use aliasing in it. :) |
| 06:31.14 | RyanE | I like using aliasing because it saves on typing long table names. |
| 06:31.55 | diskotec|w | thats the impression I got when I first saw it...save a little on the carpel tunnel |
| 06:32.30 | RyanE | yep. Table names can get pretty long, esp. if the tables were created by Java Developers. :) |
| 06:33.17 | diskotec|w | hehe. |
| 06:33.31 | diskotec|w | here is a snippet of what I was looking at.... |
| 06:33.35 | diskotec|w | SELECT TSM030_ORGANIZATION.org_ext_id, |
| 06:33.35 | diskotec|w | <PROTECTED> |
| 06:33.35 | diskotec|w | <PROTECTED> |
| 06:33.55 | diskotec|w | is grp_id considered a variable? |
| 06:34.06 | RyanE | yeah, those are long enough for me to use aliases... :) |
| 06:35.02 | RyanE | I don't know if you'd consider it a variable or not. stored procs have variables, but I don't think queries do. Of course, I'm not an SQL expert. |
| 06:35.10 | diskotec|w | Thats actually a shorter table name from all the other 700 tables in our database |
| 06:35.28 | RyanE | I've seen where they say some SQL_FUNCTION(params) as name |
| 06:35.46 | RyanE | and then the name is the name of the column. it looks like that to me. |
| 06:35.51 | RyanE | oracle? |
| 06:35.58 | diskotec|w | mssql |
| 06:36.07 | diskotec|w | bleh |
| 06:36.27 | diskotec|w | wish it were a different db but it's what I have to work with |
| 06:36.50 | RyanE | I used a lot of Sybase, which mssql was originally derived from. |
| 06:37.23 | RyanE | when i first started, that is. Haven't touched either Sybase or mssql in a lot of years. |
| 06:37.35 | diskotec|w | got any good references you could give me to learn some t-sql? |
| 06:39.03 | diskotec|w | well...guess not if you haven't touched it in years |
| 06:39.54 | RyanE | I would just google for t-sql reference |
| 06:41.11 | diskotec|w | yeah....did that. I always hit people up for information like this to see if they've had good experience with a specific source/reference. |
| 06:41.23 | RyanE | sorry, no can do this time. |
| 06:42.02 | diskotec|w | Thanks for the info....i understand that part of the select statement now. |
| 06:42.07 | diskotec|w | =) |
| 06:42.13 | RyanE | cool. |
| 06:45.55 | diskotec|w | going home now. thanks again and have a happy turkey day...don't eat too much of that triptophen (spelling?) =) |
| 06:46.30 | RyanE | 'night. |
| 06:46.37 | RyanE | 'phan, I think. |
| 06:46.46 | RyanE | so disk, where do you work, anyway? |
| 06:47.17 | diskotec|w | southern colorado.... http://www.slvrmc.org/ (no I didn't do the website) |
| 06:47.33 | RyanE | so you're up a little later than I. |
| 06:47.34 | RyanE | :) |
| 06:47.52 | RyanE | you do IS / IT? |
| 06:48.41 | diskotec|w | kinda....yeah. they are working me into a guy who creates reports and they want me to maintain a few of the databases. |
| 06:49.02 | RyanE | groovy. I avoid reporting like the plague. :) I'd rather make thing A talk to thing B. |
| 06:51.21 | diskotec|w | after I get a few of these reports created, I'm going to see if I can create a couple of php apps to present to a few different groups...I want to work more on projects like that than what they want me to do. |
| 06:51.55 | RyanE | well, sounds like a good plan. Good to grow a bit. |
| 06:52.39 | diskotec|w | yeah....i have tons of room to grow....or rather tons to learn in order to do that full time. |
| 06:52.53 | diskotec|w | well...I'd better get home....wife will probably call shortly....heh |
| 06:52.58 | RyanE | I just stopped programming PHP and MySQL full-time for 3 years. |
| 06:52.59 | diskotec|w | gnight |
| 06:53.01 | RyanE | night. |
| 16:27.01 | *** topic/#uphpu by wps -> Happy Thanksgiving |