Datenbank
Also: DB, Datenbanksystem, DBMS, Datenbanken, relationale Datenbank, RDBMS, NoSQL-Datenbank
AI-generated
A database is a structured system for the persistent storage, management, and querying of data. In intralogistics, it forms the technical foundation for WMS, ERP, and TMS by reliably maintaining master data, transactional data, and historical records.
Key facts
- A database stores logistics data – from item master data to warehouse movements – persistently and in a structured, retrievable format.
- Relational databases with ACID transaction security are widely used in WMS, ERP, and TMS because they keep concurrent write operations consistent.
- Non-relational databases are particularly well suited to large volumes of unstructured data, such as sensor or telemetry data from conveyor systems.
- High availability, backup strategy, and vendor lock-in are key selection criteria that should be evaluated as early as the system selection phase.
- Operational databases and data warehouses serve different purposes and are not substitutes for one another.
What is a database?
A database is an organized system that stores data persistently and enables structured access to it. It consists of the actual data store and a database management system (DBMS), which handles queries, write operations, access rights, and transaction security. One thing is clear: without a functioning database, no logistics system operates reliably – every posting, every storage location change, and every order header ultimately ends up in one or more databases.
Database types in the logistics environment
Relational databases (RDBMS) continue to dominate in ERP, WMS, and TMS systems. They organize data in tables with defined relationships and rely on the SQL query language. Their strengths lie in transaction security (ACID properties) and consistency under concurrent access by many users – both critical when goods receipts and issues are posted in real time.
In addition, there are non-relational databases (NoSQL), which, depending on the model, are structured as document, key-value, column, or graph databases. They are particularly well suited to large volumes of unstructured or semi-structured data, such as telemetry from conveyor systems, sensor events, or log files. Which model is the right fit depends on the use case – blanket recommendations are not appropriate here.
Relevance for warehouse planning and logistics IT
In practice, the database architecture is a decisive factor for the performance and availability of the overall system. Critical questions during planning include:
- Which data must be available in real time, and which can be processed in batches?
- How is high availability ensured – through replication, clustering, or geographic redundancy?
- How are backup, recovery, and disaster recovery organized, and what is the tolerable downtime (RTO/RPO)?
- Which systems require read or write access, and how are access conflicts avoided?
- What licensing and operating costs arise as data volumes grow?
Particularly when introducing new logistics software, the database question is often underestimated. Vendor lock-in, scaling costs, and compatibility with existing integration interfaces should be examined at an early stage.
Distinction: operational database vs. data warehouse
Operational databases manage ongoing transactions: inventory postings, order processing, and picking orders. A data warehouse, by contrast, is geared toward analysis and aggregates historical data from various sources for reporting and business intelligence. Both concepts complement each other, but pursue different optimization objectives – operational databases prioritize write speed and consistency, while data warehouses prioritize read performance and flexibility in evaluations.
Related terms
- API
An API (Application Programming Interface) is a defined interface through which two software systems can exchange data in an automated and standardized way. In intralogistics, it connects systems such as WMS, ERP, or TMS with one another and with external services.
- Artikelstammdaten
Item master data refers to the permanently valid base data of an item – such as dimensions, weight, packaging units, hazardous goods classification, and best-before date relevance. It forms the foundation for all logistical, procurement-related, and system-driven processes along the supply chain.
- BI
Business Intelligence (BI) refers to the systematic collection, preparation, and analysis of company data to support informed decision-making in logistics and supply chain management.
- Bestandsführung
Inventory management refers to the system-supported administration and continuous updating of all warehouse and material stocks within a company. It forms the basis for planning, procurement and accounting – and ensures that the book inventory and physical inventory are in agreement at all times.
- Bewegungsdaten
Movement data captures all transactions and physical goods movements in the logistics process – from goods receipt and stock transfers to dispatch. It contains timestamps, quantities, locations and the units involved, and forms the basis for transparency, control and analysis in warehouse and…
- Chargenrückverfolgung
Batch traceability refers to the complete and uninterrupted trackability of products and materials along the supply chain based on their batch assignment. It enables companies to quickly identify and selectively block all affected quantities in the event of a quality issue or recall.
- Datenanalyse
Data analysis refers to the systematic evaluation of raw data from logistics and IT systems in order to measure performance indicators, identify the causes of deviations, and make well-informed decisions.
- ERP
ERP (Enterprise Resource Planning) refers to an integrated software platform that maps core business processes such as purchasing, warehousing, production, sales, and finance within a shared system.