Comprehensive Guide to Data Management, Database Systems, and Data Security

Fundamental Concepts and Challenges in Data Management

Role of Data in Modern Society:
- Data serves as the indispensable foundation for daily operations, including the internet, smartphones, personal computers, traffic control systems, customer order processing, and corporate invoicing.
- Data is classified as a central and critical strategic asset in contemporary society.
Definitions of Information and Data:
- Information: Refers to general content describing facts, state of affairs, and operational processes.
- Data in Computer Science: Refers to information that is structured to be machine-interpretable.
- Digital data is represented at the fundamental system level using bits containing values of $0$ and $1$ , enabling computer systems to interpret and process the information.
- Data organization is required to make digital data usable across both private applications (such as watching YouTube) and professional operations (such as generating invoices).
Four Core Challenges in Data Storage and Management:
- 1. Redundancies (Redundanzen):
  - Occurs when identical data is stored multiple times across different storage locations.
  - Makes data modification highly labor-intensive and leaves the dataset error-prone.
  - Requires the same data to be manually updated in multiple locations.
  - If updates to multiply-stored data are executed in only one location, the remaining datasets become contradictory and inconsistent.
- 2. Inconsistency (Inkonsistenz):
  - Occurs when data is simultaneously edited and modified by multiple users or software programs without synchronized access control mechanisms.
  - Concrete Scenario: Two users concurrently access a checking account (Girokonto) displaying an initial balance of $\text{€2,000.00}$ . User A withdraws $\text{€1,000.00}$ and saves the transaction. Simultaneously, User B deposits $\text{€500.00}$ and saves. As a result of unsynchronized access, the database records inconsistent and incorrect values of both $\text{€1,000.00}$ and $\text{€2,500.00}$ .
- 3. Data Protection (Datenschutz):
  - Without restrictions, unauthorized read and write access across the entire dataset becomes possible.
  - Depending on the operating system utilized, data protection must be implemented through access rights management (Zugriffsrechte) or system-level encryption (Verschlüsselung).
- 4. Lack of Data Independence (Fehlende Datenunabhängigkeit):
  - Data management is typically locked to a specific application software.
  - If structural changes to the data are required, the user must modify both the application software itself and create a separate program dedicated to file restructuring.
  - If the same underlying data files need to be analyzed by a different application, a completely new, dedicated data management layer must be developed specifically for that application.

Spreadsheets vs. Database Systems

Limitations of Spreadsheet Applications:
- Spreadsheet applications (e.g., Microsoft Excel, Apple Numbers) structure data in rows and columns and excel at performing calculations or generating graphical sales charts.
- They are unsuited for storing core operational business data due to distinct performance and security limits:
  - Strict technical limits on storable data volume.
  - Data linking features (Verknüpfungsfunktionen) are cumbersome and inefficient.
  - Data can be easily manipulated because users operate directly inside the data storage layer.
  - Data evaluation and querying capabilities are severely restricted.
  - Parallel concurrent access by multiple users is only conditionally supported and frequently leads to data corruption.
  - Expanding and scaling existing data structures is complex and cumbersome.
  - High hardware and processing performance demands are placed on servers and computers when handling large tables.
Practical Workflows Comparison:
- Manual Spreadsheet Approach (Tina's Example):
  - To compile annual customer revenues in Dortmund, Tina must filter a master Excel list for her assigned customers in Dortmund, extract their customer numbers (Kundennummern), filter a separate order overview sheet (Auftragsübersicht) using those numbers, calculate individual sales using Excel functions, and manually aggregate the findings into a new document.
  - This process leads to extensive redundant entries (e.g., repeating "Johanna Food Beverage Ltd.") and requires high manual effort whenever customer details change.
- Automated Database Approach (Ralf's Example):
  - To view a customer's revenue over the past $6$ months, Ralf inputs the customer number and desired timeframe into an order management software interface (e.g., SAP).
  - The database system automatically queries and generates the overview without requiring the user to know how the data is organized internally.
  - Modifications made in master tables (such as updating Customer No. $002$ in the customer master table) automatically propagate to related transaction tables (such as invoice tables), eliminating inconsistency.
Audit-Proof Legal Storage Requirements (Revisionssichere Verwahrung):
- Under German commercial law (HGB §§ 239, 257) and tax code (AO §§ 146, 147), companies must maintain audit-proof digital storage of accounting records, including sales invoices.
- Stored records must match originals during audits and must be completely unalterable and tamper-proof.
- Database systems fulfill these digital management standards, whereas spreadsheets cannot because users can directly edit stored data values.
Direct Comparison Matrix:

Comparison Table of Spreadsheets vs Database Systems

*   **Main Goal (Hauptziel)**:
    *   Spreadsheets: Easy usage and rapid ad-hoc adaptations.
    *   Database Systems: Short access times.
*   **Data Input/Output (Dateneingabe/-ausgabe)**:
    *   Spreadsheets: Directly in file via graphical user interface.
    *   Database Systems: Executed via SQL (Structured Query Language).
*   **User Management (Usermanagement)**:
    *   Spreadsheets: Typically limited to password protection on specific sheet sections; individual user privileges are severely restricted.
    *   Database Systems: Highly granular permissions down to individual dataset/record levels depending on the software vendor.
*   **Data Volume (Datenvolumen)**:
    *   Spreadsheets: Performance degrades starting at  $1,000$  datasets; data linking becomes very slow; limited to a few Megabytes.
    *   Database Systems: Highly performant across millions of datasets; scales efficiently into the range of several Terabytes.
*   **Flexibility (Flexibilität)**:
    *   Spreadsheets: Very high; structure can be altered at any time.
    *   Database Systems: Comparatively low; structural adjustments require SQL execution within a controlled project environment.
*   **Usage / Concurrent Access (Nutzung)**:
    *   Spreadsheets: Primarily single-user; concurrent access is possible but directly causes data inconsistencies.
    *   Database Systems: Control and synchronization of parallel access is actively managed by the Database Management System (DBMS).
*   **Audit-Proof Storage (Revisionssichere Speicherung)**:
    *   Spreadsheets: Not possible because data can be modified directly by end users.
    *   Database Systems: Fully supported because direct user access to underlying data files is blocked and routed exclusively through the DBMS.

Architecture and Core Concept of Database Systems

System Components:
- A complete Database System (DBS) consists of the combination of the physical database and a Database Management System (DBMS).
- Database (DB): A collection of logically related data belonging to a specific subject domain (e.g., customer records and order records).
- Database Management System (DBMS): Software that serves as the central management interface between the database and external users or application programs (e.g., SAP).
Core Responsibilities and Advantages of a DBMS:
- Application programs do not access data files directly; instead, they submit request queries to the DBMS.
- Centralized management and access control across all users and applications.
- User administration and access rights enforcement.
- System protection against hardware and software crashes, ensuring data recovery and preventing loss during unexpected failures.
- Structural database modifications can be implemented without requiring changes to connected application programs.
- Inconsistency Avoidance: Ensures all connected application programs operate on an identical, updated data basis.
- Redundancy Avoidance: Stores data in a single centralized instance across applications.
- Data Independence & Security: Facilitates independent, parallel access to shared data under central system control.

Data Protection and Security Compliance

General Data Protection Regulation (GDPR / DSGVO) Compliance:
- Applies across the European Union to safeguard the personal data of natural persons (Art. 1 DSGVO).
- Personal Data Definition: Information that enables direct identification of a person or is classified as highly sensitive (e.g., name, birth date, gender, sexual orientation, religious affiliation).
- Rights of Individuals (Art. 15–20 DSGVO): Natural persons hold the legal right to demand disclosure, modification, or complete deletion of their personal data from corporate systems without providing justification.
- Key Principles (Art. 5 DSGVO):
  - Data Minimization (Datenminimierung): Collecting only data that is strictly necessary.
  - Purpose Limitation (Zweckbindung): Processing data strictly for specified purposes.
  - Integrity and Confidentiality (Integrität und Vertraulichkeit): Guaranteeing system security and privacy protection.
- Technical System Capabilities Required by DSGVO:
  - Capability to delete data in compliance with Art. 17 Abs. 1 DSGVO.
  - Capability to export data for data portability pursuant to Art. 20 DSGVO.
  - Implementation of Technical and Organizational Measures (TOM) to ensure system confidentiality, availability, and resilience under Art. 32 DSGVO:
    - Granular authorization models and access rights management.
    - Detailed logging and recording of database activity.
    - Pseudonymization execution capabilities.
    - Automated data breach notification mechanisms under Art. 33 DSGVO.
- Financial Penalty Scale for Violations:
  - Non-compliance with DSGVO rules can result in administrative fines of up to $\text{€20,000,000.00}$ or up to $4\%$ of a company's total worldwide annual turnover, whichever value is higher.
Corporate Data Protection and Ransomware Defense:
- Beyond personal data, enterprise databases store critical assets such as supplier details, customer records, sensitive product data, blueprints, patents, and manufacturing recipes/formulas.
- Protection against data manipulation, loss, or theft (whether caused accidentally by internal personnel or intentionally by external cyberattacks) requires explicit security measures:
  - Role-based access controls granted strictly according to employee duties.
  - Complete audit logging of all read and write database interactions.
  - Robust backup strategies paired with versioning (Versionierung).
- Versioning Definition: A process in which older states of a dataset remain archived, allowing historical data versions to be restored whenever needed.
- Essential Criteria for Backups:
  1. Spatial Separation: Storing backup copies in physical locations separate from live data.
  2. Temporal Separation: Maintaining chronological backup points/versions.
- Ransomware Defense:
  - In a ransomware attack, cybercriminals gain system access, encrypt corporate data files, and demand extortion fees (often amounting to millions of Euros) for decryption keys.
  - Without proper spatial and temporal database backups, affected businesses face insolvency or are forced to pay ransom demands to resume operations.