Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


The Art of Data Migration (ETL). Maximize Quality While Minimizing Cost (Part 1)

Maximize the return on our substantial investment by taking a structured approach and adhering to some easy rules.

Wade Walker

on 5 July 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of The Art of Data Migration (ETL). Maximize Quality While Minimizing Cost (Part 1)

What IS "ETL"? ELT?
Pretty easy really. Refers to the process of data migration.
ETL is an acronym for :
Extract (from our sources - database, spreadsheet, etc),
Transform (that is, "change" or "manipulate),
Load (to our new system(s) or other target)
Why are they important?
ETL, is a type of data migration and is the basis of any new system development that leverages existing systems
Generally speaking, the process of data migration consumes the lion's share of your project budget
The quality of the work done in ETL has a DIRECT influence on the quality of your end system. It is one of the key factors!
Data Migration
Enterprise Application Integration
Extraction Transformation and Loading
Extraction, Loading and Transformation
Wade Walker

"Real Time"
ELT is an acronym for :
Extract (from our sources - database, spreadsheet, etc),
Load (to our new system(s) or other target)
Transform (that is, "change" or "manipulate),
In short : Get this process under control, define some structure, get your team on board and your end result should be better, and leave you with more budget.

Sounds good, right?
The magic question
if it's not repeatable - it's not a methodology!
If your team fails to plan, then plan to fail
This allows you not only to identify dependencies,
and load order, but also which processes can
run in parallel
Link to Methodata's ClearView Methodology :
>Rollover and click to connect<
<Out of scope for this Prezi>
Plan. Then plan. Then start developing
Identify commonalities; areas for optimization; parameters
Document dependencies on an ongoing basis
Base Rules for Your Team
Your Team's Approach Should resemble :
Define or adopt a structured methodology
Break it up! Identify modular components
of the overall migration process that can be
reused and shared
Formally define Standards and naming conventions; Establish processes to ensure they are enforced and adhered to
More methodology detail to come...
Simple, modular mapping components
Full transcript