Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Duration 35 hours
Course Outline
Introduction, Objectives, and Migration Strategy
- Course goals, alignment with participant profiles, and success criteria.
- High-level migration approaches and associated risk considerations.
- Setup of workspaces, repositories, and lab datasets.
Day 1 — Migration Fundamentals and Architecture
- Core Lakehouse concepts, Delta Lake overview, and Databricks architecture.
- Differences between SMP and MPP and their implications for migration.
- Medallion (Bronze→Silver→Gold) design principles and Unity Catalog overview.
Day 1 Lab — Translating a Stored Procedure
- Practical migration of a sample stored procedure into a notebook.
- Mapping temporary tables and cursors to DataFrame transformations.
- Validation and comparison against original outputs.
Day 2 — Advanced Delta Lake & Incremental Loading
- ACID transactions, commit logs, versioning, and time travel features.
- Auto Loader, MERGE INTO patterns, upserts, and schema evolution.
- Optimization techniques: OPTIMIZE, VACUUM, Z-ORDER, partitioning, and storage tuning.
Day 2 Lab — Incremental Ingestion & Optimization
- Implementing Auto Loader ingestion and MERGE workflows.
- Applying OPTIMIZE, Z-ORDER, and VACUUM, followed by result validation.
- Measuring improvements in read/write performance.
Day 3 — SQL in Databricks, Performance & Debugging
- Analytical SQL features: window functions, higher-order functions, and JSON/array handling.
- Interpreting the Spark UI, DAGs, shuffles, stages, tasks, and diagnosing bottlenecks.
- Query tuning strategies: broadcast joins, hints, caching, and spill reduction.
Day 3 Lab — SQL Refactoring & Performance Tuning
- Refactoring complex SQL processes into optimized Spark SQL.
- Utilizing Spark UI traces to identify and resolve skew and shuffle issues.
- Benchmarking pre- and post-optimization performance and documenting tuning steps.
Day 4 — Tactical PySpark: Replacing Procedural Logic
- Spark execution model: driver, executors, lazy evaluation, and partitioning strategies.
- Converting loops and cursors into vectorized DataFrame operations.
- Modularization, UDFs/pandas UDFs, widgets, and creation of reusable libraries.
Day 4 Lab — Refactoring Procedural Scripts
- Refactoring procedural ETL scripts into modular PySpark notebooks.
- Introducing parametrization, unit-style tests, and reusable functions.
- Conducting code reviews and applying best-practice checklists.
Day 5 — Orchestration, End-to-End Pipeline & Best Practices
- Databricks Workflows: job design, task dependencies, triggers, and error handling.
- Designing incremental Medallion pipelines with quality rules and schema validation.
- Integration with Git (GitHub/Azure DevOps), CI, and testing strategies for PySpark logic.
Day 5 Lab — Build a Complete End-to-End Pipeline
- Assembling a Bronze→Silver→Gold pipeline orchestrated via Workflows.
- Implementing logging, auditing, retries, and automated validations.
- Executing the full pipeline, validating outputs, and preparing deployment notes.
Operationalization, Governance, and Production Readiness
- Best practices for Unity Catalog governance, lineage, and access controls.
- Cost management, cluster sizing, autoscaling, and job concurrency patterns.
- Deployment checklists, rollback strategies, and runbook creation.
Final Review, Knowledge Transfer, and Next Steps
- Participant presentations on migration work and key lessons learned.
- Gap analysis, recommended follow-up activities, and handoff of training materials.
- References, further learning paths, and support options.
Requirements
- A solid understanding of data engineering concepts.
- Proficiency in SQL and stored procedures (Synapse / SQL Server).
- Familiarity with ETL orchestration concepts (ADF or similar tools).
Target Audience
- Technology managers with a background in data engineering.
- Data engineers seeking to transition procedural OLAP logic to Lakehouse patterns.
- Platform engineers overseeing Databricks adoption.