Understand the data before you process it.
Read the data model, interview the source systems, document the domain quirks. "What does NULL mean in this column?" decides whether a migration project succeeds.
25 years of database development - domain depth in the reference projects, hands-on technical depth in the DI² side project.
Read the data model, interview the source systems, document the domain quirks. "What does NULL mean in this column?" decides whether a migration project succeeds.
Three logging levels - process, step, stack trace - queryable with a SELECT. Faulty records land in an error table, not silently in the warehouse.
Generic pipeline generation from metadata. One procedure per SQL file, every code change visible as a Git diff. Code someone can still read 18 months later.
Every industry has its own data models, its own pain points, its own stakeholders.
What stays the same: the same discipline for robust, maintainable ETL pipelines.
ETL generator from metadata - maintainable, readable, auditable. Plain SQL as output, runnable in any SQL engine. Own infrastructure on Hetzner, AI-driven development workflow.
Architect for database design and development of geodata in Postgres/PostGIS and SQL Server. Spatial analysis and data processing server-side in the database.
Performance-critical access to the control systems of melting furnaces and rolling mills. CDC against Oracle, Data Vault historization, ~500 tables from 6 plants.
Controlling of transport capacities and damage management. Reconciling planned against actual routes, damage management for carriers, vehicles and routes - complex topological logic.
Group-wide consolidation: 30 Lotus Notes apps → Microsoft Dynamics 365. 150 interfaces, 100,000+ XML files, delta migration via hash. ~3 TB data volume.
No buzzword bingo. This is the stack the five projects above were actually built with - from source-system analysis to the production pipeline.
CRM mega-migration · logistics EAI · Industry 4.0 · geodata - task, approach, outcome.
Vision, infrastructure, development workflow - how I build my own product in a structured way, from spec through UX to deploy.
Questions about data migration, ETL standards, warehouse architecture or DI² - happy to talk by e-mail or through the usual networks.