Data architecture
Platform and integration architecture, technical assessment, relational modelling, ownership boundaries and pragmatic modernisation.
Data architect · engineer · independent consultant
Erwin Vanhecke
I design, improve and troubleshoot enterprise data systems — especially where architecture, ETL, SQL Server and integration have to keep working long after the first release.
ArchitectureAssessment, design and technical direction
IntegrationETL, SSIS and enterprise data flows
Relational platformsSQL Server, T-SQL and data modelling
Production systemsPerformance, reliability and maintainability
Technical focus
Data systems that have to remain understandable.
My strongest work sits between architecture and implementation: understanding how data moves through an enterprise environment, choosing boundaries that remain maintainable, and going deep enough into the implementation to verify that the design actually works.
ETL & data integration
SSIS, source-to-target design, restartability, operational visibility, reconciliation and reliable movement between heterogeneous systems.
SQL Server
T-SQL, database design, indexing, execution plans, Query Store, Extended Events and production performance analysis.
Data warehouse environments
Operational data stores, loading layers, historical processing, marts and the relational foundations supporting reporting and analytics.
Performance & scalability
Finding the architectural, modelling and query-level causes behind slow systems instead of treating symptoms in isolation.
Hands-on engineering
Implementation where it reduces uncertainty: database code, integration flows, deployment paths, troubleshooting and production fixes.
Working approach
Pragmatic by design.
Newer is not automatically better. I prefer architecture that is proportionate to the problem, respects useful existing systems and makes trade-offs explicit.
Understand before replacing
Legacy systems often contain years of business knowledge. Replace what creates real cost or risk, not what merely looks old.
Design for failure
Failures should be visible, diagnosable and recoverable. Silent continuation is usually worse than an explicit stop.
Keep architecture close to implementation
Design decisions are stronger when they are tested against actual data volumes, failure modes, operations and deployment constraints.
Add complexity only when it earns its place
Cloud-native, distributed, NoSQL or AI components are useful when the requirement justifies them — not as default architecture decoration.
Selected experience
Long-running systems in real organisations.
The chronology below is intentionally selective. Titles and relationship wording follow publicly supportable professional-history evidence rather than being normalised into a more impressive marketing version.
Federale Pensioendienst / Service fédéral des Pensions
Database Specialist
Current work in a pension-system data environment.
AW Europe / AISIN Europe
Database Designer / Senior ETL Developer
ETL architecture, SSIS, SQL Server, T-SQL, operational data stores, datamarts, performance work and SQL Server migration coordination.
DKV Belgium
ETL Developer
ETL development in an insurance environment.
BNP Paribas Fortis
Software Developer · DBA / Business Intelligence Consultant
Application and database development followed by BI architecture, 3NF data modelling, SSIS integration, data warehouse advisory and performance work.
European Commission & European Parliament
Consultancy: support, training & development
Consulting assignments in multilingual institutional environments, including database/application development alongside support and training responsibilities.
Earlier work also includes UNIZO and other software, infrastructure and database roles. This page is a professional profile, not a complete CV.
Writing & public work
Technical notes when there is something worth saying.
I write about SQL Server, data modelling, ETL, architecture and the failure modes that appear when application and data design drift apart. I prefer a concrete technical observation over posting merely to maintain a publishing schedule.
Medium
Technical articles
Longer-form notes and practical observations on data systems and software engineering.
Read on MediumErwin & EVH Consult
The person and the consulting practice are related, not interchangeable.
I founded EVH Consult in 2012 and work through it as an independent consultant. This site is my professional profile: experience, technical focus, writing and public identities.
EVH Consult is the consulting/business presence. It owns service descriptions, project enquiries and the corporate identity. AI/R&D and Ada have their own distinct public properties as well.
Elsewhere
Public profiles.
These are the deliberate public/professional identities linked from this profile. CryptoWinne remains a separate identity and is intentionally not included here.