You’ve read about SQL Server, MySQL and PostgreSQL. Now the practical question: which one should your project use?
People often make this decision harder than it needs to be. In most cases, four simple questions give you the answer in a few minutes. This guide walks through them, with a short decision chart at the end.
Quick answer:
1. If your platform expects a database (WordPress expects MySQL), use that one.
2. If your company or team already runs one database, use it.
3. For a new web or mobile app with a free choice, use PostgreSQL.
4. For business software in a Microsoft environment, use SQL Server.
5. For a small app or tool that runs on one device, use SQLite.

Table of Contents
First: What Is a Database Server?
A database server is a program whose job is to store a database, answer queries, and keep the data safe. Your application never opens the data files itself. It sends SQL to the server, and the server sends back the rows. MySQL, PostgreSQL and SQL Server all work this way. (SQLite is the exception: it’s a library inside your app, with no separate server.)
The server can run in three kinds of place:
- On your own computer: for learning, development and testing.
- On a separate machine in your office or data centre: how many company systems run.
- In the cloud, managed for you: Amazon RDS, Azure SQL, Google Cloud SQL, Supabase or Neon run the server and handle backups and updates.
The Reassuring Part
For most small and medium projects, all the main relational databases are good enough. They all store data safely, support transactions, handle thousands of queries per second and speak standard SQL. You’re very unlikely to pick one that “can’t cope”.
What the choice really affects is how easily everything fits together: your platform, your hosting, your tools and your team. So that’s what the four questions are about.
Question 1: Does Your Platform Expect a Database?
Many platforms and frameworks either require one database or work best with one:
| Platform or framework | Database |
|---|---|
| WordPress, WooCommerce | MySQL or MariaDB |
| Joomla, Drupal | MySQL/MariaDB, PostgreSQL (Drupal also SQLite) |
| Laravel (PHP) | MySQL, MariaDB, PostgreSQL, SQL Server or SQLite |
| Django (Python) | PostgreSQL recommended; MySQL, MariaDB, SQLite, Oracle supported |
| Ruby on Rails | SQLite, PostgreSQL or MySQL |
| .NET with Entity Framework | SQL Server most common; PostgreSQL and others supported |
| Delphi with FireDAC | SQL Server, MySQL, PostgreSQL, SQLite, Firebird and more |
| Supabase | PostgreSQL (it is PostgreSQL) |
| Firebase Firestore | A NoSQL document database, not SQL |
If your platform names one database, use it, and don’t fight the platform. If it supports several (like Laravel or Delphi’s FireDAC), move on to the next question.
Question 2: What Does Your Company or Team Already Use?
This is often the most important question, and the one articles forget. If your company already runs SQL Server, with backups, monitoring and people who know how to look after it, adding a new database type means new skills, new tools and new things that can go wrong. The “best” database on paper is rarely worth that.
- Team builds on .NET, Windows Server or Azure? SQL Server fits naturally.
- Team builds PHP websites? MySQL is the usual partner.
- Team uses Python, Node.js or modern cloud tools? PostgreSQL is the common choice.
- Starting completely fresh? See Question 3.
Question 3: Where Will It Run?
- Shared web hosting: almost always MySQL or MariaDB, usually with phpMyAdmin. PostgreSQL is rare on cheap plans.
- Your own server (VPS or office server): you can install anything. Choose by the other questions.
- Microsoft Azure: Azure SQL is the natural fit, though Azure also offers managed PostgreSQL and MySQL.
- Amazon Web Services or Google Cloud: managed MySQL, PostgreSQL and SQL Server are all available.
- Supabase or Neon: PostgreSQL, with generous free plans for small projects.
- Inside the app on one device (a phone app, a desktop tool, an offline point-of-sale terminal): SQLite.
Remember licence costs too. MySQL and PostgreSQL are free. SQL Server’s Express edition is free for small databases (up to 50 GB per database in SQL Server 2025), but larger production systems need a paid licence.
Question 4: What Are You Building?
| Project | Good default | Why |
|---|---|---|
| Blog or content site | MySQL | WordPress and most PHP CMSs are built for it |
| Online shop on WooCommerce | MySQL | WooCommerce runs on WordPress |
| New web app or SaaS product | PostgreSQL | Strict data, JSONB, rich SQL, great cloud options |
| Mobile app back end | PostgreSQL (or MySQL) | Supabase gives you a database, logins and APIs quickly |
| Company business system (accounting, ERP, HR) | SQL Server | Common in business software, strong tools for backups, jobs and reporting |
| Reports and data analysis | PostgreSQL or SQL Server | Both are excellent at complex queries |
| Small desktop or mobile tool | SQLite | No server to install; the database is one file |
| Just learning SQL | PostgreSQL, MySQL or SQL Server | All three teach SQL that transfers everywhere |
The Quick Decision Chart
Does your platform require a database (e.g. WordPress)?
YES -> use that one (MySQL / MariaDB for WordPress)
Does your company or team already run a database well?
YES -> use the same one
Does the app run on a single device, with no shared server?
YES -> SQLite
Is it business software in a Microsoft / .NET / Azure environment?
YES -> SQL Server
Is it a new web, mobile or data project with a free choice?
YES -> PostgreSQL
Only shared web hosting available?
-> MySQL / MariaDB
What About Other Databases?
MariaDB
A community fork of MySQL. For everyday SQL it behaves the same, and many hosts (and XAMPP) give you MariaDB when the label says “MySQL”. Treat it as MySQL.
SQLite
A whole database in a single file, built into your app, with no server to install. It’s inside every Android and iPhone, many desktop programs and browsers. It’s excellent for small apps, tools, tests and websites with modest traffic. Its main limit: only one connection can write at a time, so busy multi-user systems are better on a database server.
Oracle Database
A powerful commercial database used by many large banks, telecoms and governments. If your employer uses it, learn it there. Otherwise, it’s not where a beginner needs to start.
NoSQL databases
MongoDB, Redis and others solve specific problems (flexible documents, caching, huge scale). Most business applications are best served by a relational database first. Types of Databases Explained shows when NoSQL makes sense.
Don’t Get Stuck Choosing
The biggest mistake isn’t choosing the “wrong” database. It’s spending weeks comparing instead of building. If you write mostly standard SQL and keep database-specific features to a minimum, moving later is a manageable project, not a disaster. Frameworks like Laravel make it even easier. Make a sensible choice with the questions above, then start.
Check Your Understanding
Which database would you choose? Decide, then check the answers.
- A new WordPress blog on shared hosting.
- A new accounting module for a company that already runs everything on SQL Server.
- A start-up’s new web app, where the team can choose freely.
- A small offline app that stores a shop’s price list on one tablet.
- A Laravel app for a client who wants zero licence costs and good cloud options.
Answers
- MySQL or MariaDB. WordPress expects it, and shared hosts provide it.
- SQL Server. Use what the company already runs and knows.
- PostgreSQL, the strong default for new projects.
- SQLite. One device, no server needed.
- PostgreSQL or MySQL. Both are free, both work with Laravel, both have managed cloud options.
Frequently Asked Questions
Which database is best for beginners?
Any of PostgreSQL, MySQL or SQL Server. The SQL you learn is about 95% the same. Choose the one used where you work or want to work, or PostgreSQL if nothing decides it for you.
Can I change my database later?
Yes. Data can be copied across with migration tools. The work is changing database-specific SQL in your application, so keeping to standard SQL from the start makes a later move much easier.
Is SQLite good enough for a website?
For small and medium websites with mostly reading and few simultaneous writes, often yes, and it’s very fast. For busy sites with many users saving data at the same moment, use a database server like PostgreSQL or MySQL.
Is a cloud database better than my own server?
A managed cloud database saves you work: backups, updates and failover are handled for you. Your own server gives you more control and can cost less if you already have the hardware and skills. Many companies use both.
What to Learn Next
- MySQL vs PostgreSQL: the two free options compared.
- SQL for Complete Beginners: start writing queries on whichever you chose.
- Database Backup and Restore: protect your data from day one.
Related articles
- What Is a Database?: the basics behind every database server.
- SQL Server vs MySQL vs PostgreSQL Cheat Sheet: the same tasks in all three.
- Types of Databases Explained: relational, document, key-value and more.