What is a database?

Database: definition and importance

A database stores information in a structured way so that it can be found, changed and analyzed quickly. Almost every business application uses one: the online store keeps products and orders in it, the CRM contacts and quotes, the inventory system stock levels. Without a database there would be no permanent user accounts, no order history and no reports.

In everyday language, the database and the database management system (DBMS) are often treated as the same thing. Strictly speaking, the database is the body of data and the DBMS is the software that manages it—for example PostgreSQL, MySQL, MariaDB or Microsoft SQL Server. The DBMS makes sure several people can work at the same time without overwriting each other’s data.

How a database works

Relational databases are the most widespread. They store data in tables with rows and columns and link them through keys: an order points to a customer instead of containing the customer’s address again every time. The data is queried and changed with the query language SQL.

Transactions make this reliable: several changes either apply completely or not at all. If an order is created and the stock level is reduced, it must not happen that only one of the two steps succeeds. Indexes speed up frequent searches like the index of a book. In addition, there are document-oriented, key-value and graph databases for special requirements.

Real-world example: from Excel chaos to a central database

A skilled-trades company with twelve employees keeps jobs, customers and material lists in several Excel files on a server. Someone regularly overwrites a colleague’s changes, customer numbers are assigned twice, files are locked because someone else still has them open, and reports have to be put together painstakingly by hand.

An application with a central database solves this: every job has a unique number, customers are recorded only once, the office and the fitters see the same up-to-date status, and permissions regulate who may change what. The old data is cleaned up and transferred during the switch.

Benefits, limits and common mistakes

A database offers consistency, simultaneous multi-user access, permissions and fast reporting. The limits lie in the effort: a clean data model has to be thought through at the start, and later changes to the structure are more laborious than in a spreadsheet. For small lists that rarely change, a database is often oversized.

• No backups, or untested ones—try out a restore in advance
• Database server reachable directly from the internet
• One account with full access for all applications
• Missing indexes, so queries slow down as the data grows
• Personal data stored without a deletion concept

What businesses should look out for

It starts with the data model, not the product choice: which objects exist, how do they relate, who may see what? Add regular, tested backups, DBMS updates, encryption and a hosting location in Germany or the EU. Nano Concepts designs data models, operates databases and migrates legacy data from Excel or old systems.