A database is an orderly collection of data, stored so that programs can quickly find, link and change it, even when many people work with it at once. Unlike an Excel spreadsheet, it enforces rules, such as that every order belongs to an existing customer. For business owners it matters most when a list turns into a business process.
How does a database work?
Most databases in everyday business are relational. They consist of tables with rows (one record, such as a customer) and columns (one attribute, such as the email address). Tables are linked through keys: every order contains the customer number, so the system finds all of a customer's orders immediately. The query language for this is called SQL.
The database also checks rules. It ensures that a customer number exists only once, that a date looks like a date and that no order is left behind for a deleted customer. Well-known systems are PostgreSQL, MySQL and MariaDB, and the lightweight SQLite.
Where are the limits of Excel?
A spreadsheet is ideal for lists, calculations and quick analyses. Problems arise when several people work at once, data is linked or the list grows. Errors then pile up: duplicate customers, overwritten cells, sorted columns where one column did not move along, and file names like "customer_list_final_new2".
| Criterion | Spreadsheet (Excel) | Database |
|---|---|---|
| Simultaneous editing | Prone to conflicts and copies | Designed for it, changes are reconciled |
| Links between data | By hand, error-prone | Secured through keys and rules |
| Access rights | Per file | Per user, table or action |
| Data volume | Gets slow as it grows | Built for large volumes |
| Traceability | Low | Logs and history possible |
| Set-up | Instant | Needs planning |
Excel is enough when one person keeps a manageable list and nobody else changes it. As soon as the list becomes a shared store, the step to a database pays off, usually hidden inside an application such as a CRM, shop or booking system.
How do you back up your database?
A database often holds your most important capital: customers, orders, invoices. Lose it and the business stands still. The rule of thumb is 3-2-1: three copies of the data, on two different storage media, one of them in a different place. It is a widespread recommendation, not a law. Add automatic backups, encryption of the backup copies and access for only a few people.
You protect personal data under Art. 32 GDPR with appropriate technical and organisational measures. These include access rights, encryption and backups. This is not legal advice. You will find more about customer data in When is a CRM worth it for a small business?.
When do you need a database of your own?
You already use databases without seeing them: in your website's CMS, in the shop or in the booking tool. You need one tailored to your process when your data is spread across several tables, lists and programs and you want to combine it, analyse it or pass it on to other systems automatically. Programs talk to each other through interfaces, as described in What is an API?.
At WebDrift, such solutions come under our business systems service, from €3,900 plus €149 a month for hosting and support. All prices are final prices under § 19 UStG.
- List drawn up of every place where customer and order data lives
- Shared spreadsheets with several editors marked as a risk
- Automatic backup set up, with a copy in another location
- Restore tested at least once
- Access rights assigned by task
- Data protection and deletion periods clarified
Conclusion: organise first, then protect
A database is not witchcraft but orderly bookkeeping for data. Check where your most important data lives and secure it so that you can bring it back in an emergency. If your spreadsheets are hitting their limits, describe your process.
