Anyone here have a job which involves a lot of SQL Commands?

A lot of Indian developers have lots of buzzwords on their CVs and claim to know it all, but when actually given a problem to solve will struggle with it.
If you can apply your knowledge and think for yourself then you'll stand above a lot of them.

As for SQL, I've worked with Oracle, SQL Server, Sybase, DB2 and MySQL at various points over my career.
Once you get your head round thinking of data in terms of sets and operations on those sets you shouldn't have any issues with SQL.
Personally I find most database stuff boring these days and try to steer clear of it if I can help it.

I know DB can be veeeery boring lol but sometimes boring is good and im a boring guy to be honest lol

What kind of roles do you enjoy?
 
The thing is, most SQL stuff is fairly similar, what matters is knowledge of the data structures and where to go.

This, the relationships/structures of the data is one of the most important things to know but this is normally unique to the company.
 
Last edited:
Do i need maths? Lol!
What math based queries will i do?
Im way past the degree stage! Been there done that.
Just never used SQL although i loved it back in Uni..wanna get back into it!

Oh yes - Indian developers are KILLING IT!
These guys know the whole framework at such a young age (ASP,SQL,C# VB Etc)
Trust me, few Indian developers that claim to know everything really do. A lot of development work is learning on the job and so it should be.

If you want to learn SQL you first need to understand how a relational database works, how to normalize data etc.

After that find a sample database and set yourself some tests. e.g. find all customers that haven't placed and order this month, Find the supplier who you bought the most stock from over a year. Make them more and more difficult until you feel comfortable and then find some online test to push you a bit further.
 
This, the relationships/structures of the data is one of the most important things to know but this is normally unique to the company.

This is true, but (assuming the company has a reasonable database designer/team) the approach taken will probably follow one of the common schema styles depending on the purpose of the database in question.
 
This is true, but (assuming the company has a reasonable database designer/team) the approach taken will probably follow one of the common schema styles depending on the purpose of the database in question.
Hmm, I wish. My company has been tring to implement a 20m SKU Entity Attribute Value schema for about a year now. It's been an interesting experience. They've now junked that idea for something which is even more ingenious, but equally unfathomable from a traditional point of view.
 
Hmm, I wish. My company has been tring to implement a 20m SKU Entity Attribute Value schema for about a year now. It's been an interesting experience. They've now junked that idea for something which is even more ingenious, but equally unfathomable from a traditional point of view.

EAV is freaking terrible, we can't wait to be rid of it in our new database structure.
 
EAV is freaking terrible, we can't wait to be rid of it in our new database structure.
Strictly is wasn't pure EAV. Pure EAV wouldn't have performed with the amount of data we have. I agree though, if implemented we would have lived to regret it rather quickly. The problem is we need a something flexible so a compromise will have to be made.
 
I'm an Oracle DBA, have been for years.

Go to http://www.oracle.com/technetwork/index.html, and register an account.

Click on Downloads and download and install what ever you want, Oracle 11g, Applications Servers, SQL Developer, JDeveloper. Then click on Documentation and download the documentation.

Then play and learn.

As long as you don't use the software commercially you have access to all of Oracle's software.
 
I wanna chat with some people about jobs that use SQL and the ways in which you use it etc.

Well thats it really, like, if you work for said company, what do you with SQL? What kind of commands do you use and what for?

Not creating databases - I dont wanna know about that just yet.
Existing DB only.

I use them a lot, looks ups (select * from yada yada yada), inserts, and updates to manipulat existing data. We then use said data across a set of front-end platforms.

If I'm honest, you'll eventually build up your own archive of common statements, just save them either on the DB itself, or in a text file. Soon enough you'll find actually writing the statements becomes redundant (and I've gotten quite lazy bearing in mind this paragraph lol).

I use a lot of unix too, all the basic tripe though, cd/mkdir/del/ls -lrt blah blah blah

honestly though, if there is anything you need or don't get, you can teach yourself the command and its purpose in literally 90 seconds lol

for my first 'technical' role requiring basic SQL/UNIX, I literally just sat in the office one morning and taught myself all the basics. It can seem daunting but depending on what degree is required initially, it can be relatively simple to pick up!

disclaimer: not intending to downforce anyones job/experience in SQL at all, this is my own personal experience with the language and the level which is required in my job (I don't dev/create DB's at all, purely manipulation against existing stuff!)
 
Last edited:
Back
Top Bottom