Skip to main content

Walkthrough · Beginner · 5 minutes

How to Create a MySQL Database

A database, a user, and the privileges tying them together — the three things every installer asks for — a hands-on walkthrough in plain words that names the classic mistake before you reach it.

The short answer

The job: a database, a user, and the privileges tying them together — the three things every installer asks for. Time to set aside: 5 minutes. Skill needed: beginner.

Below is the full run of steps, the error most people trip over, and the short cut worth remembering. On Hosting & Domains plans several steps are already automated away — the guide marks each one.

By the Hosting & Domains team · Reviewed 18 August 2026

Beginner

Skill rating

5 minutes

Time budget

5

Steps in total

24/7

Support on call

No technical background needed. This walkthrough was written for first-timers, proven on our own hardware, and honest about which parts are genuinely tricky rather than merely unfamiliar.

First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.

The outline first, then the detail

Set out end to end, the route is: use the database wizard, choose a name you will still understand later, let the panel generate the password, then save it, give the user full privileges on its database and write down the four connection values.

No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.

The well-worn snag

Creating the database and the user but skipping the privilege grant. The app returns 'access denied', which looks precisely like a mistyped password even when both credentials are perfect. Check the grant before you chase anything else.

Forewarned is genuinely forearmed here. This one mistake accounts for most of the frustration the topic ever causes — and it disappears entirely once somebody points it out.

A habit worth borrowing

One application, one database, always. Two apps sharing a database saves nothing and turns every backup, restore and cleanup into an argument about which tables belong to whom.

Habits this small are what separate the people who find hosting effortless from the people who find it draining. The same tools on both sides — a different way of working.

Where this platform takes work off you

Steps that never deserved your time are taken out: certificates issue and reissue themselves, the installer handles application setup, the daily copy absorbs the what-ifs, and per-site settings live in a panel rather than a configuration file. The guide covers the remainder — the part that is actually about your site.

Should a step still misfire, support answers at any hour with an actual fix rather than a knowledge-base link and a shrug. Half the guides on this site began as repeat patterns in our ticket queue.

One control panel running the hosting and the names side by side

Why this job is shorter on our plans

Tutorials written against imaginary hosting go stale fast. Ours are written against the real thing: the same panel, installer and defaults waiting in your account.

Hosted somewhere else already? We move the whole site at no charge, usually within 24 hours, and it goes on answering visitors throughout.

  • Every step checked exactly as published
  • The snag named before it arrives
  • The dull steps taken out of your way
  • People reachable at any hour you stall

Why Hosting & Domains

Standard on every plan

Every undo written out

Any step that could bite is marked, together with the exact way to wind it back.

The snag, flagged up front

The classic error for this particular task is named before step one, which is how 5 minutes stays 5 minutes.

Works exactly as printed

Every step is proven on the platform we run — none of the 'your host may vary' hedging.

Help that keeps your hours, not ours

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

5 steps, nothing padded

Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.

Honest about how big it is

A database, a user, and the privileges tying them together — the three things every installer asks for is a beginner-level job — set aside 5 minutes, with the platform-absorbed steps marked.

Quick Start

Order placed to site online

  1. 1

    Use the database wizard

    The wizard takes the three jobs in order: database created, user created, privileges granted. Doing it by hand is exactly how one of the three quietly goes missing.

  2. 2

    Choose a name you will still understand later

    The panel adds your account name as a prefix automatically (account_projectname), so make your half describe the contents. Come back in six months and 'db1' or 'test' tells you nothing at all.

  3. 3

    Let the panel generate the password, then save it

    Generate it in the panel and put it into your password manager and the app's config file. Database credentials are infrastructure and nobody should be memorising them.

  4. 4

    Give the user full privileges on its database

    An application wants full authority over its own database. Limited accounts exist for good reasons, read-only reporting among them, but installation is not one of those reasons.

  5. 5

    Write down the four connection values

    Host (localhost where the app runs on the same server), database name, username, password. Those four answers cover every installer form you will ever meet.

Built In

Fitted to every plan

  • LiteSpeed caching in the server itself rather than bolted on by plugin
  • DDoS filtering absorbed at the network edge
  • cPanel, which is what most of the industry already runs
  • Spam and virus screening on every mailbox by default
  • 99.9% uptime as the target, watched around the clock
  • WordPress Toolkit, with the updates seen to for you
  • WebP image optimisation built in, at no extra charge
  • Your existing site brought across by our engineers, at no charge
  • A daily copy, with restores you run yourself from the panel
  • NVMe SSD storage on every tier, not only the dear ones

Frequently Asked

The questions that come up most

Should the host field say localhost or the server name?

Use localhost wherever the application sits on the same hosting account. Connecting from a desktop MySQL client means the server hostname, and only once your IP is registered under Remote MySQL, because external access is switched on deliberately rather than by default.

What can I use to look inside the database?

phpMyAdmin, sitting beside the database tools in the panel, lays every table and row out visually. It is the standard window onto everything your application has written since the day it was installed.

How do I read my mail away from my desk?

Webmail runs in any browser, and every mailbox also speaks IMAP, POP and SMTP — so the app on your phone, the client on your desk and webmail stay in step, showing the same messages in the same state.

How do payments and auto-renewal work?

You pay by credit or debit card through a secure checkout, and renewals bill at the same rate as the original order. Every invoice sits in your client area, and auto-renewal switches off with a toggle in the account — no telephone call needed.

Keep reading

  • How to Choose a Domain Name

    Land on a name that still sounds right after years of saying it every day — beginner level, about an evening of thought.

  • How to Restore From a Backup

    Get files, database, or both back without panic, and no further back than necessary — beginner level, about 10–30 minutes.

  • Database (Glossary)

    The plain-English definition this page rests on, with a worked example.

  • Secure Hosting

    Imunify360, isolated accounts and hardened defaults for security-first builds.

  • Web Hosting

    cPanel hosting on NVMe drives — SSL, the migration and year one of the name all included.

Changing hosts? Run through our checklist first.

A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.

What arrives is the checklist, and then the occasional note on keeping a site quick. Leave whenever you like; the privacy policy covers the rest.

The name is waiting.

Free SSL, a free migration, renewals billed at the original rate, and people on support around the clock. That is the whole of it.

View Secure Hosting plans