Firstly, what the hell is SQL?

Hopefully you’ve heard of it in some shape or form or else you wouldn’t be here. But let’s clear up one of the most common (and community dividing) misconceptions first.

As far as I’m concerned, it’s pronounced Sequel. There will be many amongst the data analyst community who will fill your head with nonsense that it should be pronounced one letter at a time (ESS QUEUE ELLE). But they don’t know their EH ESS ESS from their EE ELLE BEE OH DOUBLE YOU.

Asking the expert.

SQL was developed by Donald Chamberlin and Raymond Boyce at IBM in the 1970s. Patrick Gillespie saved us a lot of time back in 2012 by having the great idea of emailing Don Chamberlin and just asking him outright which was correct. He created the language. We can only assume his would be the most definitive answer on the subject.

Patrick quotes the response he got in his article, Pronouncing SQL – S Q L or Sequel:

Hi Pat,

Since the language was originally named SEQUEL, many people continued to pronounce the name that way after it was shortened to SQL. Both pronunciations are widely used and recognized. As to which is more “official”, I guess the authority would be the ISO Standard, which is spelled (and presumably pronounced) S-Q-L.

Thanks for your interest,

Don Chamberlin

Don is clearly a gentleman in suggesting that the ISO Standard way is now more authoritative. But seeing as he sticks with his own original pronunciation himself, I’m going to go with that too.

Fight the good fight. Tell them you were schooled early.

We’ve started off on the right foot now and got the important issue out of the way upfront. So let’s get into the bones of it.

If that’s how we say it, what exactly is it?

SQL stands for Structured Query Language.

It lets us take things out of relational database systems, put new rows of data into them, amend records that are in there and remove records we don’t need any more.

It was recognised as the standard language for relational databases by the American National Standards Institute way back in 1986.

If it’s a standard, does that mean I only have to learn it once and can use it everywhere?

No, of course not. If things were that simple I wouldn’t need to write this series to get aspiring analysts over the first SQL hurdle.

All of the main relational database management systems use a form of SQL. They mainly have some variations in syntax and functionality as you delve deeper into them though.

If some heads hit the desk there at the mention of syntax and RDBMSes please take a second to freshen yourselves up. I want to make the point that learning SQL doesn’t have to be boring.

It’s not exactly touring with Led Zeppelin in the 1970s exciting either. But it doesn’t have to be the dry, dusty insomnia cure most places make it. Not by a long chalk.

In this ongoing series, we are going to look at many areas of SQL.

This will include the main SQL commands such as SELECT, UPDATE, INSERT INTO and DELETE. We’ll look at functions such as SUM, COUNT and AVG. We’ll delve into joining tables using JOINS such as INNER JOIN, LEFT and RIGHT JOIN, OUTER JOIN and CROSS JOIN.

Added together, this knowledge will give you a major head-start on your way to becoming a SQL Grand Master.

Buckle up, it’s going to be a wild ride.

Check out the next lesson from my Learn SQL For Data Analysis series.

Want articles like this in your inbox each week?

Straight talking, real world analytics stories, lessons and tips. Don't miss out.