A database is where your website keeps everything that isn't a static file: posts, products, user accounts, settings, comments. If you run WordPress, WooCommerce, or almost any dynamic app, the pages you see are built by pulling rows out of a database and dropping them into a template. MySQL and MariaDB are the two database engines you'll run into on Flashcloud hosting, and for almost every practical purpose they behave the same way and speak the same language.
You manage your databases from MySQL Databases in the portal, or directly through phpMyAdmin in cPanel if you need to look at or edit the actual data.
MySQL vs MariaDB: does it matter which one you have?
MariaDB started as a fork of MySQL, built by the original MySQL developers after Oracle acquired it. It's designed to be a drop-in replacement: same connection protocol, same SQL syntax, same command-line tools, same file formats. WordPress, WooCommerce, and virtually every PHP application on the market support both without any code changes. If you're not sure which one your account runs, it doesn't change how you interact with it day to day, whether that's through phpMyAdmin or an application's built-in database settings.
Tables, rows, and why "structured" matters
A database is organized into tables, and each table is organized into rows and columns, similar to a spreadsheet. A WordPress site, for example, keeps a table for posts, a table for users, a table for comments, and several more, each with columns defined for the kind of data that belongs there. This structure is what makes databases fast: instead of scanning every file on disk to find "posts published in 2026," the database can jump straight to the relevant rows using indexes built on those columns.
This is also why a database is different from just storing content in files. Files are good for things that don't change often, like images or your site's HTML and CSS. A database is built for content that gets queried, filtered, sorted, and updated constantly, often by many visitors at once.
How your application talks to its database
Applications connect using three pieces of information: a database name, a database username, and a password, along with a host (usually localhost on shared hosting, since the database server runs alongside your website). WordPress stores these in wp-config.php; other apps have their own config file or setup wizard that asks for the same details.
Each database also needs at least one user assigned to it with permission to read and write data. Creating the database and creating the user are two separate steps, and a common setup mistake is creating both but forgetting to attach the user to the database, which leaves the application unable to connect. On most hosting accounts, this is handled from the portal's database tools.
When you'd actually open phpMyAdmin
Most of the time your application manages its own database automatically. You'd open phpMyAdmin when you need to:
- Search and replace a URL across every table after moving a site to a new domain
- Export a full backup of the database as a
.sqlfile before making risky changes - Check table sizes when a site is running slow or storage is filling up
Back up before editing anything directly. phpMyAdmin lets you run raw SQL against your data, and there's no undo on a bad query. Export the table (or the whole database) first, then make your change.
When to contact support
If a database won't connect, a query is timing out, or you're not sure whether a change in phpMyAdmin is safe to make, open a ticket from the portal. Our support team can look at the actual error and the database involved rather than guess from a description.