Database terminology is full of pronunciation debates — SQL, PostgreSQL, schema, tuple. This exercise clarifies what is genuinely accepted versus what is simply wrong.
0 / 5 completed
1 / 5
A developer asks in an interview: "Have you worked with SQL databases?" Which pronunciation(s) of SQL are accepted in professional contexts?
SQL — both "S-Q-L" and "sequel" are correct:
This is one of the most debated pronunciation questions in IT. The answer is: both are standard.
/ˈɛskjuːˈɛl/ — "S-Q-L" — spell out each letter. Used in formal presentations, documentation discussions, and when first introducing the term
/ˈsiːkwəl/ — "sequel" — pronounced as a word. This comes from SQL's predecessor "SEQUEL" (Structured English QUEry Language), developed at IBM in the 1970s. Very common in conversational developer English
Historical context: SQL was originally called SEQUEL, then shortened to SQL for trademark reasons. The "sequel" pronunciation stuck and remains common today.
Context clues for which to use:
Context
Preferred
Formal interview or presentation
"S-Q-L" — more formal, unambiguous
Casual team conversation
Either — "sequel" is very common
Reading "MySQL" aloud
"my S-Q-L" or "my sequel" — both fine
2 / 5
A backend developer mentions the database: "We're migrating from MySQL to PostgreSQL." How is MySQL correctly pronounced?
MySQL — "my-S-Q-L" or "my-sequel" — both correct:
The name MySQL was chosen by co-founder Michael Widenius, who named it after his daughter "My". So it's always "My" + SQL:
"my-S-Q-L" — /ˈmaɪ ɛskjuːˈɛl/ — formal, spells out SQL
"my-sequel" — /ˈmaɪ ˈsiːkwəl/ — casual, treats SQL as a word
Common mistake to avoid: "my-SKOOL" — this incorrectly merges the letters. The "S", "Q", and "L" don't collapse into "skool". Each letter is either spelt out or the "sequel" word form is used.
The MySQL family of names:
MySQL — "my S-Q-L" or "my sequel"
MariaDB — "muh-REE-uh dee-bee" (also named after Widenius's daughter Maria)
InnoDB — "IN-oh-dee-bee" (the storage engine)
3 / 5
A data engineer says: "Our data warehouse runs on PostgreSQL." How should PostgreSQL be pronounced?
PostgreSQL — "POST-gres S-Q-L" or just "Postgres":
PostgreSQL has a notoriously tricky name. Here's the breakdown:
Full name: /ˈpoʊstɡrɛs ɛskjuːˈɛl/ — "POST-gres S-Q-L"
Informal shorthand: /ˈpoʊstɡrɛs/ — just "Postgres" — extremely common in team conversations
Syllable breakdown of "PostgreSQL": POST · gres · S · Q · L
"POST" — /poʊst/ — like "post office"
"gres" — /ɡrɛs/ — rhymes with "dress" (NOT "grees")
"S-Q-L" — either spelled out or "sequel"
Fun fact: PostgreSQL is named after POSTGRES, which was itself named after INGRES — all database systems developed at UC Berkeley. The "Post" = successor to INGRES.
Practical tip: In most team conversations, just say "Postgres" — everyone will know what you mean, and you avoid the full pronunciation challenge. Both are professional:
"We use Postgres as our primary database" ✓
"The PostgreSQL connection pool is configured in..." ✓
4 / 5
A developer reviews a PR and comments: "The database schema needs updating to add the new user field." How is schema pronounced?
schema — /ˈskiːmə/ — "SKEE-muh":
The word schema comes from Greek (σχῆμα, "form, plan"). The "sch" combination in Greek-origin English words makes a /sk/ sound:
Correct: /ˈskiːmə/ — "SKEE-muh" — starts with /sk/
Wrong: /ˈʃiːmə/ — "SHEE-muh" — this is the German pronunciation (Schema in German = "shay-mah")
The "sch = /sk/" rule in English (Greek-origin words):
Word
Pronunciation
IT context
schema
/ˈskiːmə/ "SKEE-muh"
"database schema", "JSON schema"
schematic
/skɪˈmætɪk/ "ski-MAT-ik"
"circuit schematic"
Schema in IT contexts:
"database schema" — the structure of tables and relations
"JSON Schema" — a vocabulary to validate JSON documents
"GraphQL schema" — type definitions in GraphQL
"schema migration" — changing the database structure
5 / 5
In a Python discussion, a developer says: "A database tuple is an immutable row of values." Which pronunciation(s) of tuple are accepted?
tuple — /ˈtʌpəl/ or /ˈtjuːpəl/ — both accepted:
This is one of the most genuinely debated pronunciations in programming. There is no single "correct" answer:
Pronunciation
Sounds like
Common among
/ˈtʌpəl/ — "TUP-ul"
Rhymes with "supple"
Many Python developers, mathematicians
/ˈtjuːpəl/ — "TYOO-pul"
Rhymes with "pupil"
Some mathematicians, database people
Origin of the debate: The word "tuple" comes from mathematical suffixes: double, triple, quadruple, quintuple... The "tup-" pronunciation follows from "quinTUPle" (quin-TUP-ul), while "tyoo-pul" follows the "-uple" pronunciation pattern.
Practical advice:
In a team, use whichever form your colleagues use — consistency matters more than "correctness"
In Python circles, "TUP-ul" is very common
In database/SQL contexts, "TYOO-pul" is heard more often
Both will be understood everywhere
Compound forms:
"named tuple" /ˈneɪmd ˈtʌpəl/ — "a named TUP-ul"
"tuple unpacking" — unpacking a tuple into variables
What will I practice in "SQL and Database Term Pronunciation — Pronunciation Practice"?
This is a Intermediate pronunciation exercise with 5 questions focused on the correct pronunciation, stress, and sounds of mispronunciations used in IT.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This exercise has 5 questions. A progress bar at the top tracks how many you've answered, and each question gives immediate feedback with an explanation.
Do I need audio or a microphone for this exercise?
No — this is a multiple-choice recognition exercise. It tests whether you can identify correct stress, sounds, and pronunciation patterns, not whether you can record your own speech.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed.
What if I don't understand why an answer is correct?
Read the explanation shown after you answer each question — it breaks down the correct pronunciation in plain English. You can also check the site Glossary for related terms.
Who is this exercise for?
It's designed for non-native English speakers in IT roles who want to sound clearer saying mispronunciations in meetings, code reviews, and interviews.
Where can I find more Mispronunciations pronunciation exercises?
See the Mispronunciations section for related exercises, or browse the main Pronunciation hub for other subcategories.
Can this help me prepare for a technical interview?
Yes — clear pronunciation of technical terms matters in interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.