SQL (Not a help request)
-
While working on my resume, I talked to few friends about the issue. All of them mentioned SQL as a knowledge skill. However, all of them had completely different level of knowledge. What is the common level of required knowledge of SQL at real world work places? Basic select statement, complex joins with grouping, ability to write SQL parser/optimizer from memory???
Paul's right, it depends. I think it largely depends on the job and the work environment. If you will be working with a DBA, you probably just need to know basic SQL (select, update, insert, delete) and be able to deal with simple joins an unions. If you will be required to do database design or maintain a database, you will need to understand normalization, index structures. constraints, performance profiling, SQL query optimization, backup and restore procedures, etc. The first set of skills I mentioned is (for the most part) non-DB specific. These skills can be applied to SQL Server, Access, DB2, etc. I think this is why some developers list all the various databases on their resumes. These second set of skills requires the first plus is more DB specific (except for normalization). The way DB2 deals with indexes is different from SQL Server. If someone listed DB2 or ORACLE as a skill I would be expecting this level of comprehension. If they listed SQL, I would just be expecting them to be able to write queries. Felix Gartsman wrote: ability to write SQL parser/optimizer from memory??? I doubt this is a skill most employers are looking for.
-
Paul Watson wrote: I personally can write SQL statements by hand up to simple unions and joins. Complex ones though I resort to the Query Builder. I would not expect more from a programmer I hire, unless they were for a db position. Query Builders are evil, can I recommend a book I recentily read 'Oracle High Performance SQL Tuning' it opened my eyes to just how much optimisation is available. IMHO if you don't know the diff between you cost and rule based SQL optimisation you should take be on the next train to siberia. Regards Ray "Je Suis Mort De Rire"
Ray Kinsella wrote: Query Builders are evil, can I recommend a book I recentily read 'Oracle High Performance SQL Tuning' it opened my eyes to just how much optimisation is available. IMHO if you don't know the diff between you cost and rule based SQL optimisation you should take be on the next train to siberia. So what time is the next train to Siberia and I hear it is cold there, so warm clothes I guess? ;) I agree Query Builders are evil if you are building a performance critical, ten gazillion user scalable app. In that case you will have enough dosh to hire a pro db designer to do the optimisation etc. etc. But for everyday SQL the Query Builder does fine and you can always use Query Analyzer to do some rough optimisation checking and tweak a few little things. Not all projects warrant a db expert unfortunatley. I wish I could use our db guy on even the smallest project, but he is expensive and time is money. It's that whole project triangle thing in MSF. Cost vs. Time vs. Features. regards, Paul Watson Bluegrass Cape Town, South Africa The greatest thing you'll ever learn is just to love, and to be loved in return - Moulin Rouge Tim Smith wrote: Over here in the third world of humor (a.k.a. BBC America), peterchen wrote: We should petition microsoft to a "target=_Paul" attribute.
-
Paul Watson wrote: I personally can write SQL statements by hand up to simple unions and joins. Complex ones though I resort to the Query Builder. I would not expect more from a programmer I hire, unless they were for a db position. Query Builders are evil, can I recommend a book I recentily read 'Oracle High Performance SQL Tuning' it opened my eyes to just how much optimisation is available. IMHO if you don't know the diff between you cost and rule based SQL optimisation you should take be on the next train to siberia. Regards Ray "Je Suis Mort De Rire"
Ray Kinsella wrote: IMHO if you don't know the diff between you cost and rule based SQL optimisation you should take be on the next train to siberia. Please enlighten me, I use MSSQL Server and am not aware of this. Nick Parker
Actually, real programmers don't need the enter key- they just type in 00001101."
-
Ray Kinsella wrote: IMHO if you don't know the diff between you cost and rule based SQL optimisation you should take be on the next train to siberia. Please enlighten me, I use MSSQL Server and am not aware of this. Nick Parker
Actually, real programmers don't need the enter key- they just type in 00001101."
I know nothing about SQL server but I expect it probabily relies on a cost based optimizer Regards Ray "Je Suis Mort De Rire"
-
I know nothing about SQL server but I expect it probabily relies on a cost based optimizer Regards Ray "Je Suis Mort De Rire"
Ray Kinsella wrote: probabily relies on a cost based optimizer Yeap, right on target :-) The Sql2000 server optimizer is a great cost based optimizer ! The query optimizer is much smarter . I'm not astonished since they contrated Oracle enginners to work on Sql 7.0 that was a major improvement to the crappy Sql Server 6.5 . Cheers, Joao Vaz A person who is nice to you, but rude to the waiter, is not a nice person - Natalie Portman (Padme/Amidala of Star Wars)
-
Ray Kinsella wrote: IMHO if you don't know the diff between you cost and rule based SQL optimisation you should take be on the next train to siberia. Please enlighten me, I use MSSQL Server and am not aware of this. Nick Parker
Actually, real programmers don't need the enter key- they just type in 00001101."
Nick , SQL Server uses a cost based optimizer and it's based on the costs that the query optimizer decides on. I recommend you the best ever SQL book of the market , IMHO , Inside Sql Server 2000, this baby rocks, and your knowlege will increase to great levels. It explains the behaviour of the query optimizer , a lot of optimizing tips , inside information about the inner workings of SQL and so much great stuff ! Definitely even for reference , this book , rocks ! If you can't buy one copie, steal it, it's worth the crime :-D Cheers, Joao Vaz A person who is nice to you, but rude to the waiter, is not a nice person - Natalie Portman (Padme/Amidala of Star Wars)
-
While working on my resume, I talked to few friends about the issue. All of them mentioned SQL as a knowledge skill. However, all of them had completely different level of knowledge. What is the common level of required knowledge of SQL at real world work places? Basic select statement, complex joins with grouping, ability to write SQL parser/optimizer from memory???
I haven't used Oracle, so I can't say much on that. But, for SQL Server I'd say you'd definitely want to know some T-SQL and a bit on stored procedures. Using transactions is paramount in ensuring data integrity at times. Jeremy L. Falcon Homepage : Sonork = 100.16311
Perseverance pushes past painful promenades - providing precious peace. Surely some striving souls survive symptomatic stress? Maybe my mangling might misguide malicious miscreants? -
Would some of its teachings apply to 7 because that's what we are still using at work? I assume it would, but I'd like to make sure before I adopt a new loved one (a.k.a.; book). Jeremy L. Falcon Homepage : Sonork = 100.16311
Perseverance pushes past painful promenades - providing precious peace. Surely some striving souls survive symptomatic stress? Maybe my mangling might misguide malicious miscreants?95 % still aply for 7 :-) Sql 2000, was a minor upgrade , compared with 7 :-) Now , I'll go to cinema ! Nuff said ! :omg: Cheers, Joao Vaz A person who is nice to you, but rude to the waiter, is not a nice person - Natalie Portman (Padme/Amidala of Star Wars)
-
Nick , SQL Server uses a cost based optimizer and it's based on the costs that the query optimizer decides on. I recommend you the best ever SQL book of the market , IMHO , Inside Sql Server 2000, this baby rocks, and your knowlege will increase to great levels. It explains the behaviour of the query optimizer , a lot of optimizing tips , inside information about the inner workings of SQL and so much great stuff ! Definitely even for reference , this book , rocks ! If you can't buy one copie, steal it, it's worth the crime :-D Cheers, Joao Vaz A person who is nice to you, but rude to the waiter, is not a nice person - Natalie Portman (Padme/Amidala of Star Wars)
Would some of its teachings apply to 7 because that's what we are still using at work? I assume it would, but I'd like to make sure before I adopt a new loved one (a.k.a.; book). Jeremy L. Falcon Homepage : Sonork = 100.16311
Perseverance pushes past painful promenades - providing precious peace. Surely some striving souls survive symptomatic stress? Maybe my mangling might misguide malicious miscreants? -
While working on my resume, I talked to few friends about the issue. All of them mentioned SQL as a knowledge skill. However, all of them had completely different level of knowledge. What is the common level of required knowledge of SQL at real world work places? Basic select statement, complex joins with grouping, ability to write SQL parser/optimizer from memory???
IMO if you are doing programming and can do fairly complex joins then you have enough knowledge to do most real world database programming. SQL is pretty straightforward so even if there was something you didn't know it would not take long to pick it up. -- Dana Holt Xenos Software