Skip to main content
.com domains from $2.99 — WHOIS privacy at no extra charge

How-to · Beginner · 5 minutes

How to Create a MySQL Database

Everything you need to a database, a user, and the privileges that join them — the trio every application asks for — the steps in order, the snag to watch, and the tip our support desk gives everybody.

Straight answer first

The job: a database, a user, and the privileges that join them — the trio every application asks for. Time to allow: 5 minutes. Skill needed: beginner.

The walkthrough below covers every step, the mistake most people make, and the shortcut worth keeping. On Hosting Seller plans several of these steps are already done for you, and we say where.

Written by the Hosting Seller staff · Checked 1 August 2026

Beginner

Difficulty level

5 minutes

Time to allow

5

Stages

24/7

Help at any hour

You do not need to be technical for this. The walkthrough is written for first-timers, tested on our own platform, and honest about which parts are genuinely fiddly and which are merely unfamiliar.

Rule of the road: read the snag section before you begin rather than after. It is harvested from the tickets of people who did it the other way round.

The overview before the detail

Here is the route in full: let the database wizard drive, give it a name you will recognise later, generate the password, then file it, grant the user full rights on that database and write down the four connection details.

No stage needs code or a terminal unless the guide says so outright, and where it does, the exact commands are printed. The full step-by-step sits below; the sections around it give the context that makes it stick.

The classic snag

Creating the database and the user, then forgetting to grant privileges. The application reports 'access denied', which reads like a wrong password even though both credentials are perfect. Check the grant before you touch anything else.

Forewarned really is forearmed here. This one mistake accounts for most of the frustration the subject produces, and it is entirely avoidable once somebody names it.

The trick worth borrowing

Give every application its own database. Sharing one between two apps saves nothing at all and turns every backup, restore and tidy-up into a negotiation about whose rows are whose.

Small habits like this are the real difference between people who find hosting easy and people who find it stressful. The tools are identical; the working method is not.

How our platform shortens this

We have automated the steps that do not deserve your time: certificates issue and reissue themselves, the installer handles application setup, the daily backup covers the what-if, and per-site settings live in a panel instead of a config file. The guide above covers what remains — the part that is actually about your site.

And when a step misbehaves anyway, support answers at any hour with the actual fix, not a knowledge-base link and a shrug. Half our best guides began life as a pattern in the ticket queue.

Someone running a hosting account from the cPanel dashboard

A good platform makes every guide shorter

Tutorials age badly when they are written against imaginary hosting. These are written against ours: the same panel, the same installer and the same defaults you will meet.

What you pay on day one is what you pay at renewal, so the year-two invoice holds no surprises worth opening early.

  • Step by step, tested exactly as printed
  • The snag flagged before you reach it
  • The dull steps are already automated
  • People on hand at any hour if you stall

Why Hosting Seller

On every plan, as standard

The undo is always named

Where a step could bite, the guide says so and tells you how to put it back again.

The snag, named early

The classic mistake for this exact job is flagged before step one, so 5 minutes stays 5 minutes.

Works exactly as written

Every step tested on the platform we run — no 'your host may differ' hand-waving anywhere.

Help on the counter

Stuck on step three at midnight? Support answers at any hour, mid-guide included.

5 steps, no filler

Each stage is a few minutes of steady clicking, with the fiddly parts marked as fiddly.

Scoped honestly

A database, a user, and the privileges that join them — the trio every application asks for is a beginner-level task — this guide budgets 5 minutes and says which steps the platform absorbs.

First Steps

From choosing to live

  1. 1

    Let the database wizard drive

    The wizard runs the three jobs in order: create the database, create the user, grant the privileges. Doing it by hand is exactly where one of the three quietly gets left out.

  2. 2

    Give it a name you will recognise later

    cPanel adds the account prefix automatically (account_projectname); the part you choose should say what it holds. Six months on, 'db1' and 'test' are pure guesswork.

  3. 3

    Generate the password, then file it

    Let the panel generate it, then paste it into your password manager and into the application's config. It is plumbing, not something anybody should be keeping in their head.

  4. 4

    Grant the user full rights on that database

    Applications expect complete control of their own database. Restricted accounts have their uses — a read-only reporting login, say — but this is not one of them.

  5. 5

    Write down the four connection details

    Host (localhost on the same server), database name, username, password. Every installer you will ever meet asks for exactly those four values and nothing else.

In the Box

Packed with every plan

  • Webmail in the browser plus IMAP, POP and SMTP for your own client
  • SSH, Git and Composer on the plans built for developers
  • Staging copies so changes get tested before they go live
  • The Softaculous installer for one-click application setup
  • Site migration done for you by our staff, at no charge
  • LiteSpeed caching running at the server, not bolted on by plugin
  • A backup taken daily, with restores you run yourself
  • DDoS filtering handled out at the network edge
  • A free SSL certificate on every plan, reissued before it lapses
  • Nothing added at setup — no joining fee, ever

Across the Counter

The questions we get asked most

Is the database host localhost or the server name?

localhost for anything running on the same hosting account. A desktop MySQL client connecting from outside uses the server hostname, and your address has to be added under Remote MySQL first — that access is switched on deliberately, never by default.

How do I look inside the database?

phpMyAdmin, linked beside the database tools, shows every table and row on screen. It is the standard window onto whatever your application has been quietly storing since the day you installed it.

How do I read the mail when I am away from the desk?

Webmail opens in any browser, and every mailbox also speaks IMAP, POP and SMTP — so the mail app on your phone, the client on your desktop and webmail all show the same messages in the same order.

How do I pay, and does it bill again on its own?

Orders go through a secure checkout by credit or debit card, and the renewal is taken at the same price you first paid. Every invoice sits in the client area for you to read, and switching auto-renewal off is a toggle in your account rather than a phone call.

Are backups included, and can I put one back myself?

A backup is taken daily on every plan, and the restore is yours to run from the panel in minutes — files, databases or both, at three in the morning without waiting on a ticket. Keeping your own copy offsite as well is never a bad habit, and nothing here stops you.

Does the price climb when the term is up?

No. What you pay to order is what you pay to renew, year after year. We do not run teaser rates, so there is no year-two ambush waiting in the calendar, and your bookkeeping can treat the hosting line as a fixed number.

What happens to my files if I leave?

The site and the files stay yours. Pull a full backup from the panel whenever you like, before or during cancellation. Domains remain registered in your name for the term you paid for and can move to any registrar once the standard 60-day window has passed.

Packing up and moving host? Take our checklist.

A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.

One email carrying the checklist, then the odd note on running a site well. Step off the list whenever you like — our privacy policy spells out the rest.

Whenever you're ready to order.

Quick NVMe hosting, SSL and the move in included, and real people on the counter at any hour — on a price that doesn't shift.

See the plans