What is a SQL database?
Corbin Brown
3 min read
Part of the Vibe Coding Fundamentals video series on YouTube.
A SQL database is where your app keeps everything it needs to remember — users, orders, messages, settings. Close the browser tab and your app forgets nothing, because none of it lived in the tab. It lived in the database. If you're vibe coding anything beyond a single static page, your agent is going to bring up the database within the first hour, so it's worth knowing what it's talking about.
Spreadsheets that answer questions
Picture a workbook of spreadsheets. One sheet lists your users — one row per person, columns for name, email, signup date. Another sheet lists orders. A SQL database is that, with a superpower: the sheets can answer questions about each other. “Show me every order from users who signed up this month” is one line of SQL, and the database answers it across millions of rows in milliseconds. SQL — Structured Query Language — is just the phrasing of the question.
The good news for builders: you almost never write SQL yourself anymore. Your AI agent writes it. Your job is knowing what the database is so you can sanity-check the plan — which tables exist, what connects to what, and where the data actually lives.
What this means for your project
- When your agent says “schema,” it means the list of tables and their columns — the shape of your app's memory. Ask to see it in plain language before agreeing to changes.
- Names you'll meet: Postgres and MySQL are SQL databases you host somewhere; Supabase and Neon are companies that host Postgres for you. Same idea, different wrapper.
- The one rule that saves real pain: never let an agent run destructive database changes (deleting tables, wiping columns) without a backup. Data is the one thing a code revert can't bring back.
FAQ
Do I need a database for my project?
If your app remembers anything between visits — accounts, saved items, submissions — yes. If it's a purely informational site where every visitor sees the same content, no, and adding one is complexity you don't need.
SQL vs NoSQL — do I care?
Not at the start. SQL tables are the default for a reason: they're structured, agents are excellent at them, and every hosting platform supports them. If a project genuinely needs something else, your agent will say so and you can ask it to explain why.