Skip to main content

Glossary Entry

What is Database?

Database without the jargon — the definition, the analogy, and why any site owner should care.

The short answer

Think of a database as queryable structured storage, the ordered memory holding a site's content, users and transactions, kept separate from the code that operates on them.

What follows: the longer explanation, a picture that holds, the practical stakes, and the places you will genuinely meet it.

By the Hosting & Domains team · Reviewed 18 August 2026

100+

Terms in the jargon buster

2 min

Average read time

Plain

English throughout

24/7

People, if you get stuck

That separation is the whole architecture, with the code in the files defining how things behave and the database recording what has actually happened. Hosting is dominated by relational engines such as MySQL and PostgreSQL, which hold everything in tables you can interrogate.

That single split explains why 'back up the site' is really two jobs, why promoting a staging copy has to work around whatever live has collected meanwhile, and why a restore is never files or database but always both.

The everyday parallel

The operations manual against the flight log. How the service is run is in the manual, while what actually flew, when, and with whom aboard is in the log. Lose the manual and you write it again. Lose the log and the operation no longer remembers its own history.

Carry that picture with you and most documentation on the topic loses its mystery on a first read.

What genuinely rides on it

Almost no hosting job avoids this line. Migrations, backups, staging, clear-outs and post-compromise cleanups all go wrong the moment somebody treats files and data as one object.

That, incidentally, is the bar for any technical term — not 'could I lecture on it' but 'would I recognise it as the answer to my problem'. For this one, you now would.

One worked example

Migrating means two moves: wp-content travels as files, and the database arrives as an imported dump. Two artefacts make one site, and leaving either half out gives you something site-shaped and hollow.

Entirely unremarkable once you have seen it — which is the point: most hosting ideas are plain machinery behind an intimidating label.

How Hosting & Domains deals with it

Here it largely looks after itself, since the defaults are sensible and the panel puts the controls within reach the moment you want them. Read on: MySQL, Backup, Staging Environment and PHP.

Order an annual plan and the first year of the name's registration is on us.

A developer at the terminal with real SSH access to the box

A jargon buster from the people who answer the tickets

Sooner or later every confusing hosting term turns into a support ticket, so we defined the hundred commonest ones properly — once, in the same plain English we use with customers.

NVMe storage and LiteSpeed caching sit under every tier, the smallest plan included — that is the floor here, not an upgrade.

  • 100+ entries, plain English all the way
  • Ordinary analogies, working examples
  • Neighbouring ideas linked together
  • Written by our own support engineers

Why Hosting & Domains

Standard on every plan

This term, properly landed

Database defined, pictured by analogy and located in your own panel — recognise-level after a single read.

Tied to real hosting

Examples name platforms you would genuinely use, never an abstract diagram on a whiteboard.

The next step, drawn out

Carry on into MySQL and Backup — ideas rarely travel alone, so the neighbours are linked in.

Jargon-free by design

Definitions written for people who run sites, not for other sysadmins — translation rather than restatement.

Stakes made explicit

More than what a thing is: the moments it turns out to be the answer to a problem you have.

Clear about how deep to go

Most of these are recognise-level rather than operate-level, and every entry says which it is.

Quick Start

Order placed to site online

  1. 1

    Find it in your own account

    Nothing teaches a hosting term faster than finding it in your own panel; five minutes of looking beats an hour of reading.

  2. 2

    Check the defaults as they stand

    Look at how your account has it configured. Nine times in ten the default is right, and a check turns the guess into certainty.

  3. 3

    Chase the neighbouring terms

    Hosting terms travel in groups — MySQL, Backup and Staging Environment finish this one's picture, each a two-minute read away.

Built In

Fitted to every plan

  • Your existing site brought across by our engineers, at no charge
  • PHP versions set per site from the control panel
  • No set-up charge at any point, and no joining fee
  • LiteSpeed caching in the server itself rather than bolted on by plugin
  • WordPress Toolkit, with the updates seen to for you
  • WordPress and 400+ further applications installed in one click
  • Free SSL on every plan, reissued before the old one lapses
  • SSH, Git and Composer on the developer plans
  • Staging copies for trying a change before it goes live
  • Money back within 30 days on hosting plans, 7 on reseller

Frequently Asked

The questions that come up most

Why should a website need a database?

Because things change: content gets edited, users sign in, orders accumulate. Purely static sites do without one and run on files. As soon as content is managed rather than hand-edited, something is doing that managing, and it is a database.

Is hand-editing the database ever acceptable?

phpMyAdmin allows it, provided you keep to the rules: export before touching anything, do routine work through the application's own screens, and save hand edits for the surgical cases such as a password reset or a repair, where nothing else fits.

Do plans include copies I can restore myself?

Yes — every plan gets a daily copy, and the restore runs from your panel in minutes: files, databases or both, at three in the morning with no ticket queue in the way. Keeping a further copy offsite is still a sound habit, and nothing here stops you.

What is the uptime commitment, and what happens in a month that misses it?

99.9% — and if a month falls below that through a fault on our side, our terms entitle you to a pro-rated credit; ask and we apply it. Calling it a target rather than a contractual SLA is a deliberate choice. Hardware and network faults surface through platform monitoring, usually before the first customer notices.

Keep reading

  • Staging Environment

    A staging environment is a private duplicate of your live site where changes get tried out before any visit…

  • MySQL

    MySQL is the relational database beneath most hosted applications, the structured store holding every WordP…

  • How to Optimize a MySQL Database

    The way it is really done, in order, with the usual mistake pointed out.

  • Web Hosting

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

  • WordPress Hosting

    WordPress looked after for you — LiteSpeed caching, staging copies and a daily backup.

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.

Start on a plan priced without games.

From a first website to a rack of machines, moving up is a change to the account rather than a migration.

View Web Hosting plans