DWHPro · Enterprise data engineering

Data engineering project experience

Migration, pipeline development and enterprise reporting: the context, contribution and delivery behind our published project accounts.

Discuss your project

These accounts describe work delivered in client environments by DWHPro and specialists in its network. They show the type of engineering involved; individual responsibilities and reference availability should be discussed for a new engagement. Client identities are withheld here.

Retail warehouse migration: Teradata to Snowflake

Situation and constraints

A Swiss retailer needed to move its enterprise data warehouse while maintaining the business results used for inventory, sales and supply-chain reporting. The source and target architectures required more than SQL syntax conversion.

Contribution described in the project account

The work covered analysis of the Teradata workload, target data models, rebuilding critical ETL pipelines, automated reconciliation and knowledge transfer to the internal team.

Validation

Source-to-target comparisons included row counts, aggregates and business-logic checks. Matching row counts alone would not establish that operational or financial totals were correct. Discrepancies were investigated before cutover.

Reported outcome

The published account records production workloads moving to Snowflake, no data loss reported across the migrated datasets, and training for the internal team. These are project-specific reported outcomes, not a guarantee for another migration.

Technologies: Teradata, Snowflake, Python, ETL/ELT and dbt.

Explore the migration service.

Data pipelines for financial research

Situation and constraints

A US investment research environment required reliable integration of multiple financial data sources and checks supporting downstream research models.

Specialist contribution

The project account describes a senior engineer working within the client’s research team on production pipelines, automated validation, data quality checks, monitoring and transformation documentation. The wider research platform remained a client-team responsibility.

Delivery described

The account records pipeline development and testing work using Python and SQL. No independently verified numerical reliability or investment-performance result is published here.

Explore data engineering and integration.

Enterprise warehouse migration in banking

Situation and constraints

A Frankfurt banking operation needed to modernise an established warehouse while preserving critical reporting dependencies.

Specialist contribution

The account describes a senior architect combining architecture, development and project coordination: mapping sources and dependencies, rebuilding pipelines, validating outputs, coordinating parallel operation and transferring knowledge.

Delivery described

The reported scope includes a migrated warehouse and a maintainable target architecture. Acceptance criteria and outcomes for a new project must be established separately.

Technologies: Teradata, SQL Server, ETL/ELT, Data Vault and Python.

Regulatory reporting and reusable warehouse frameworks

Situation and constraints

A European banking environment needed regulatory reporting interfaces and repeatable warehouse engineering patterns across multiple reporting domains.

Specialist contribution

The account describes work on FATCA, CRS and other regulatory interfaces, alongside historisation, surrogate-key and data quality frameworks. It also includes SQL tuning and support for controlled post-load adjustments.

Delivery described

Reusable frameworks and reporting interfaces were incorporated into the client environment. This account illustrates the engineering scope without promising a generic percentage improvement or regulatory outcome.

Technologies: Teradata, IBM DataStage, workload scheduling, SQL and Git.

Explore Teradata tuning.

Billing data warehouse modernisation

Situation and constraints

An Austrian telecommunications environment needed to evolve billing and usage data models while preparing for a billing-system change.

Specialist contribution

The account describes data-model changes, work on data quality and campaign analytics, and dependency analysis for the new billing system.

Delivery described

The work supported changes to analytical domains and preparation for a controlled transition. Client-specific operational results are not generalised into promises for other engagements.

Technologies: Teradata, SQL and enterprise data modelling.

Discuss the experience relevant to your project

Tell us which platform, industry and delivery responsibilities matter to you. We can discuss the relevant specialist’s contribution and what supporting detail may be shared, subject to client confidentiality and permission.

Discuss your data challenge

Tell us about your current platform, the problem and any important deadlines. We will agree the next step with you.

Discuss your project

Protected by Security by CleanTalk and CleanTalk Anti-Spam