Scribd
Upload
10 views18 pages

DataMigration Scenario

Uploaded by

Hariharan A
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
10 views18 pages

DataMigration Scenario

Uploaded by

Hariharan A
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 18

Data Migration Scenario

Data Migration
Project Scenario

This data migration project involves moving a data warehouse from one
database to another. Client is a Banking and Financial services firm with
terabytes of customer data, plans to transfer data from legacy system
(out of date database system) to a modern storage
Data Migration Process
• Data Backup
• Data Profiling
• Data Modelling
• Data Mapping
• Data Migration
• Migration Testing
Data Profiling
• Identify data sources (Docs, spreadsheets, RBDMS packages, txt files)
• Tagging data with keywords, description and categories
• Prepare reports with descriptive statistics (row, column count, data
types, length, min, max, count, recurring patterns etc.)
• Perform data quality assessment
• Discover Metadata and assess accuracy
• Identify key candidates, foreign key candidates, functional
dependencies and perform inter-table analysis
Data Modelling
• Understand business need and requirements
• Establish primary key, foreign key, alternate keys etc.
• Understand entities, attributes and relationships
• Establish cardinalities (1:1, 1:M, M:M)
• Resolve redundancies and anomalies (Normalize data)
• Assist architects and developers in creating Physical Data model
Project Scenario – Data Modelling for Client data
• Build Physical Data model for Banking customer data with entities,
attributes, primary key, foreign key, constraints, views, indexes etc.
• Prepare Entity Relationship Diagram (ER Diagram)
• Establish association between entities with cardinalities (One to One,
One to Many, Many to One, Many to Many )
Scenario – Physical Data model
Trans Num: INT (PK)
Account Num: INT (FK)
Card Num : INT (FK)
Amount : INT
Date : DATETIME
Transactions

Account Num: INT (PK) Cust ID: INT (PK) NOT NULL Card Num: INT (PK)
Account Name: VAR Account Num: INT (FK) Card Name: VAR CHAR
CHAR (20) Card Num: INT (FK) (20)
Account Bal : INT Trans Num : INT (FK) Credit Limit: INT
Credit Limit: INT First Name: VAR CHAR (20) Amount : INT
Date : DATETIME Last Name: VAR CHAR (20) Date : DATETIME
DOB: DATETIME
Gender: VARCHAR (10)
Accounts Credit Cards
Customers
Scenario – Entity Relationship Diagram
Name Address Email
Trans
Num

Trans
Customer Orders Transaction Amount

Trans
Date
Account
Credit card
Order
Checking Savings
Num Num
CC
Amount
Name
Acc. Bal
Credit
Shopping cart
limit
Data Mapping
• Identify components of target schema, database, table name, column
name, datatype, Slowly Changing Dimensions etc.
• Identify components of source database, table name, column name,
datatype
• Establish business transformation rules
• Build a mapping document
• Map Source to target
Scenario – Data Mapping
Use column intelligence - Find out which columns were system generated,
conformed, derived or mapped “as is” from source
System Generated

1:1
Scenario – Data Mapping
Derived

Conformed
Scenario – Data Mapping
Use Table intelligence - Find out which tables are direct copies from
source
System Generated

Join – Perform Join on tables as per business rules and requirements


Scenario – Data Mapping
Load – Load tables to Target database

Notes
• Include notes with dates and decisions with reasons for change
Scenario – Data Mapping
Derive DDL from mapping and generate the code with simple formulas
Data Migration
• Plan Migration strategy
• Data Sources Analysis
• Design and Build Migration Solution
• Execution
• Testing
• Revision and Maintenance
Role of BA
Scenario – Data Migration P – Primary
S - Secondary

• Pre – Migration
Activities: Data Assessment (P), Data Cleansing, Extract, Transform, Load
Output : Scope & Migration strategy(P), Cleaned Source data, ETL jobs,
migration scripts
• Migration
Activities: Verify record counts(P), Fix exceptions or issues(P)
Output : Signed off Migration document (P)
• Post Migration
Activities: Documentation(P), Quality reports(P), system reports (P), signoff
(P)
Output: Signed off Migration closure document (P)
Role of BA

Migration Testing P – Primary


S - Secondary

• Check Data Security & Integrity (P)


• Check Transfer times (P)
• Hardware/ Software compatibility (P)
• Functional and Nonfunctional aspects of application are met post
data integration (P)
Thank You

You might also like