PowerDesigner is a modeling tool that can be used to model various aspects of an enterprise data management system. It allows users to create conceptual data models, logical data models, physical data models, data movement models, and more. The presentation discussed how PowerDesigner can be used to model the migration of an OLTP database to a data warehouse, including reverse engineering the source database, generating models for the data warehouse, defining transformations, and generating scripts to move data. It concluded that PowerDesigner and a model-driven approach can accelerate development and increase productivity for data warehouse projects.

1. Enterprise Data Management
SAP ANALYTICS & INNOVATION FORUM '12
Mehmet ÇAVUŞ, Sybase, Technical Consultant
16.03.2012
1

2. The Modeling Environment - Domains
The Modeling Environment
© 2012 SAP AG. All rights reserved. 2

3. PowerDesigner Architecture
© 2012 SAP AG. All rights reserved. 3

4. Conceptual Model (CDM) / Logical Data Model(LDM)
PowerDesigner Models
Fulfills the following roles:
– Represents the overall logical structure of a data, independent of any
software or data storage structure - system and business domain,
– Gives a formal representation of the data structure needed to run an
enterprise or a business process/service,
– Uses ER, Merise and IDEF1X notations,
– Uses only one conceptual data diagram,
– Represents the organization of data in a graphical format,
– Imports/Exports Data Items and Entities from BPM
© 2012 SAP AG. All rights reserved. 4

5. Conceptual Data Model (CDM) / Logical Data Model(LDM)
PowerDesigner Models
Employee
Employee Identifier <pi> ID <M> •Standard E/R modeling
Employee Name <ai> NAME
Employee Description <ai> L_TEXT
Identifier_1 <pi> •Business rules, domains, data
Identifier_2 <ai>
...
items, entities, relationships,
associations, identifiers, inheritance
Sales Stock_Clerk
Salary MNY
Commission MNY
Hourly Rate MNY
•Supports one-to-many & many-to-
Shipper many relationships
Salary MNY
•Automatic physical data model
Orders generation
OrderID <pi> ID <M>
Description L_TEXT <M>
Identifier_1 <pi>
...
Customer Items
Address ADDR
ItemsID <pi> ID <M>
CustomerID <pi> ID <M>
Description L_TEXT
Name MNY
Identifier_1 <pi>
Phone PHN ...
Identifier_1 <pi>
...
© 2012 SAP AG. All rights reserved. 5

6. Physical Data Model (PDM)
PowerDesigner Models
Represents the implementation of physical structure of a data for selected
(R)DBMS including data storage structure and management choices or
parameters (particularities of DBMS),
It gives a formal representation of the physical data structure to be installed
and actively used within the IT system,
Uses standardized relational or multidimensional notation,
The PDM fills the following roles:
– Represents the organization of physical data in a graphical format,
– Verifies the validity of data design for selected (R)DBMS,
– Holds all (R)DBMS related choices and particularities,
– Used for repository generation, synchronization and administration,
– Facilitate O/R, used with framework, and R/R mapping from DWH
© 2012 SAP AG. All rights reserved. 6

7. Multi-Dimension Data Warehouse Design
Star Schema Location
Product Location ID integer <pk> Time
Country varchar(30) Time ID integer <pk>
Product ID integer <pk>
City varchar(30) Year integer
Name varchar(30)
Month integer
Day integer
Sales Country_City_Location
Sales ID integer <pk> Country ID <h:1>
Product ID integer <fk1>
Location ID integer <fk2>
...
Country Name
City ID
City Name
<h:2> Multi-dimension
Country
Country ID integer
Country Name varchar(30)
<pk>
Zip
Location ID <h:3> Model
Hierarchy_1 <Default> <h>
City Sales - Country_City_Location
Product Category City ID integer <pk> Month_Time
Month
Category ID integer <pk> Country ID integer <fk>
Month Number integer <pk> Month Number <h:1>
Category Name varchar(30) City Name varchar(30)
Month Name varchar(10) Sales Month Name
Zip varchar(30)
Sales - Month_Time
Time ID <h:2>
Sales ID
Sales number Year
Month
Sales Day
Location Time Hierarchy_1 <Default> <h>
Product
Location ID integer <pk> Sales - Product Category_Product
Product ID integer <pk> Time ID integer <pk>
City ID integer <fk>
Category ID integer <fk> Month Number integer <fk>
Name varchar(30) Year integer
Month integer Product Category_Product
Day integer
Category ID <h:1>
Snowflake Sales ID
Sales
integer <pk>
Category Name
Product ID
Name
<h:2>
Schema Product ID integer <fk1>
Location ID integer <fk2>
...
Hierarchy_1 <Default> <h>
© 2012 SAP AG. All rights reserved. 7

8. Physical Data Model (PDM)
PowerDesigner Models
Oracle 8i, 8i2, 9i, 9i2, 10g, 10gR2 and 11g support
•Bitmap join indexes Oracle Database Packages
•Global Temporary Tables “Undo” Tablespaces and Storage Partitions
•Abstract Data Types Oracle Materialized Views
•Oracle Dimension support
...
IBM DB/2 5.x, 6, 7, 8 and 9 for OS/390 and Common Server support
•Detailed Tablespace definitions Column LOB options
•Tables with Computed Columns Generated and Encrypted Value declarations,
•DB/2 index Bind Packages DB/2 Materialized Query Tables
...
Microsoft SQL Server 7.x, 2000, 2005 and 2008 support
•Indexed Views with encryption options Multiple file definitions for filegroups
•Row Global Unique Identifier Constraint and Collation names
•Identity properties Replication settings
•Microsoft Analysis Services including cubes
...
Adabas, AS400, Informix, MySQL, Netezza, PostgreSQL, Teradata ...
© 2012 SAP AG. All rights reserved. 8

9. Data Movement Model (DMM)
PowerDesigner Models
High level physical view of information (data) movement/flow processes,
either through replication or any other data flow,
– Replication as a process where transactions performed on one (source)
database are propagated asynchronously to one or more target database in
a serialized manner,
It gives physical view of information sources, destination, applied
transformations, replication processes and source/destination data
structure mappings,
Uses simple graphical notation,
The DMM is used for the following roles:
– To present data flows, transformations, data sources and destination,
– To describe replication process for Replication Server or Mobilink,
– To document DWH ETL/delivery flows and used mappings,
– Allows direct access to every data model used within the flow
© 2012 SAP AG. All rights reserved. 9

10. Data Movement Model (DMM)
PowerDesigner Models
© 2012 SAP AG. All rights reserved. 10

11. Impact Analysis in PowerDesigner
© 2012 SAP AG. All rights reserved. 12

12. PowerDesigner
Reporting – Report Generator
Powerful report generator
Multi-model
Customizable
Template-based
Easy-to-use, drag-and-drop interface
Generates RTF or HTML
© 2012 SAP AG. All rights reserved. 13

13. Repository Architecture
We need a good metadata repository
•Team development
 Security to protect elements,
core, library, etc.
 Single source for all
elements (find and reuse)
•Model management
 Versioning
 Branching
 Compare/Merge
 Reporting
 Enterprise Glossary & Library.
 Impact Analysis in Repository.
© 2012 SAP AG. All rights reserved. 14

14. Repository Portal
© 2012 SAP AG. All rights reserved. 15

15. DataWarehousing Architecture
2
1
© 2012 SAP AG. All rights reserved. 16

16. Migrating an OLTP Database to a Data Warehouse
To establish a data warehouse using an OLTP database
I. Reverse engineer the OLTP database with statistics
II. Generate/Create an DW Physical Data Model (PDM)
 Modify DW model using indexes based on statistics, denormalization, etc...
 Define the transformation between source and DW models using either mapping or
DMM
III. Generate the data warehouse
IV. Move data from OLTP database to DW by
 Generating export/import scripts to run on OLTP database and DW
 Creating ETL templates
© 2012 SAP AG. All rights reserved. 17

17. 1- Reverse Engineering the OLTP Database with Statistics
PowerDesigner allows users to reverse engineer statistics data (number of
rows, number of distinct values for a column, …)
© 2012 SAP AG. All rights reserved. 18

18. 2- Generating Physical Data Model (PDM) for DW
PowerDesigner allows users to generate new models using link and synch
methodology.
© 2012 SAP AG. All rights reserved. 19

19. >Define the transformation by DMM or Mapping
© 2012 SAP AG. All rights reserved. 20

20. 3- Generating the Data Warehouse Database
Generate the data warehouse database using the Database>“Generate
Database” command.
© 2012 SAP AG. All rights reserved. 21

21. 4- Example of an Export & Load Script
© 2012 SAP AG. All rights reserved. 22

22. Powerdesigner Modeling
Information Architecture
© 2012 SAP AG. All rights reserved. 23

23. Our Customer’s Perspective…
© 2012 SAP AG. All rights reserved. 24

24. Turkcell Success Story
“It was an amazing success of
Turkcell, the leading mobile phone operator in Turkey, Sybase PowerDesigner.”
previously kept conceptual, logical, physical data,
ETL process modeling,
Yuksel Guler,
source to target mapping relations information been in
Microsoft® Word, Visio and Excel. Using Sybase PowerDesigner, Turkcell Communication Service A.fi.,
Turkcell is able to manage all modeling requirements Service and Product Development
within BIS-Reengineering project.
Business Advantage
Turkcell is able to develop impact analysis on changes made
in any department, and provide information on changes
that affect underlying metadata.
Key Benefits
•Reduces business process modeling time by 40%
•Saves 30% in labor efforts
•Provides compatibility with other software
•Increases specifications for projects in a single modeling tool
•Synchronizes with Microsoft® Word for business process modeling (BPM)
© 2012 SAP AG. All rights reserved. 25

25. Conclusion
Using PowerDesigner and Model-Driven Approach can greatly accelerate the
development, increase the productivity and reduce errors for data warehouse
design and implementation.
© 2012 SAP AG. All rights reserved. 26

26. Thank you
Mehmet ÇAVUŞ
Technical Consultant
mehmet.cavus@sybase.com.tr
+90 (0) 212 351 27 30