1. Database Design with Oracle SQL
Developer Data Modeler
Heli Helskyaho, Miracle Finland Oy
Wildcard
13.9.2013
© Miracle Finland Oy

2. Introduction, Heli
• Graduated from Helsinki University (Master of Science,
computer science)
• Worked with Oracle products since 1993, worked for IT since
1990
• Database!
• CEO for Kantamestarit Oy since 2000
• CEO for Miracle Finland Oy since 10/2010
• Board member for OUGF since 2001
• Chairperson for OUGF since 2007 (vice-chair for years before
that)
• Ambassador/Spokesperson for EOUC since late 2007
• Oracle ACE since 2011
© Miracle Finland Oy

3. Introduction, Heli
• Been an Oracle Designer user since 1996 and
Data Modeler user since 2010
• Been solving performance problems since
1993
– Absolutely convinced that good database design
and documentation will reduce this work.
– Absolutely convinced that it is easier to solve
problems on database that has been documented
© Miracle Finland Oy

4. What is database design?
• 4 (5) phases, over and over again
– Requirement analysis (DM: logical)
– Conceptual design (DM: logical)
– Logical design (DM: relational)
– Physical design (DM: physical)
– (Transaction design) (DM: process)
© Miracle Finland Oy

5. What is Data Modeler?
• A tool for database design (supports all the ”new”
Oracle features)
• Logical, relational, physical models, DDLs,…
• Multidimensional models (DW), Data Flows etc.
• For designing and documenting the data architecture
and the database
• Support for all the phases in database design and easy
moving from one to another, support for reverse
engineering
• Support for version control and multiuser environment:
XML files and Subversion
© Miracle Finland Oy

6. What is Data Modeler?
• Import: Oracle repository, existing databases,
Oracle Designer, file import (Erwin, Bachman), …
• Export: DDL, CSV, …
• Reporting (in tool itself and also Reporting
Repository)
• Standards: Design Rules, Preferences, Naming
Standards, Domains, …
• Data Modeler integrated in SQL Developer (3.0 -
>), also reports
© Miracle Finland Oy

7. SQL Developer Data Modeler,
technical overview
• Support for:
– Windows (XP, Vista, Windows 7 including x64), Linux, Mac OSX
– Oracle 9.2.0.1 ->
– IBM DB2 V7 ->, Microsoft SQL Server 2000 ->
– ODBC/JDBC
• The following requirements must be met to install and run
correctly:
– JavaTM 1.6 or higher Standard Edition Runtime Environment
– About 125 MB on Hard Disk
– 512 MB at a minimum, 1 GB RAM is recommended
© Miracle Finland Oy

8. © Miracle Finland Oy

9. Logical model
© Miracle Finland Oy

10. © Miracle Finland Oy

11. Entity
© Miracle Finland Oy

12. © Miracle Finland Oy

13. © Miracle Finland Oy

14. © Finland OyMiracle

15. © Miracle Finland Oy

16. Relationship
© Miracle Finland Oy

17. © Miracle Finland Oy

18. © Miracle Finland Oy

19. From logical to relational
© Miracle Finland Oy

20. © Miracle Finland Oy

21. © Miracle Finland Oy

22. © Miracle Finland Oy

23. © Miracle Finland Oy

24. © Miracle Finland Oy

25. © Miracle Finland Oy

26. © Miracle Finland Oy

27. © Miracle Finland Oy

28. Relational model
© Miracle Finland Oy

29. © Miracle Finland Oy

30. Table
© Miracle Finland Oy

31. © Miracle Finland Oy

32. © Miracle Finland Oy

33. © Miracle Finland Oy

34. © Miracle Finland Oy

35. © Miracle Finland Oy

36. © Miracle Finland Oy

37. Column
© Miracle Finland Oy

38. © Miracle Finland Oy

39. © Miracle Finland Oy

40. Primary Key
© Miracle Finland Oy

41. © Miracle Finland Oy

42. Foreign Key
© Miracle Finland Oy

43. © Miracle Finland Oy

44. © Miracle Finland Oy

45. From relational to physical
© Miracle Finland Oy

46. © Miracle Finland Oy

47. © Miracle Finland Oy

48. © Miracle Finland Oy

49. © Miracle Finland Oy

50. © Miracle Finland Oy

51. © Miracle Finland Oy

52. © Miracle Finland Oy

53. Physical model
© Miracle Finland Oy

54. © Miracle Finland Oy

55. Properties
© Miracle Finland Oy

56. © Miracle Finland Oy

57. © Miracle Finland Oy

58. © Miracle Finland Oy

59. © Miracle Finland Oy

60. © Miracle Finland Oy

61. © Miracle Finland Oy

62. © Miracle Finland Oy

63. Physical to DDLs
© Miracle Finland Oy

64. © Miracle Finland Oy

65. © Miracle Finland Oy

66. © Miracle Finland Oy

67. © Miracle Finland Oy

68. © Miracle Finland Oy

69. © Miracle Finland Oy

70. © Miracle Finland Oy

71. Other functionalities
© Miracle Finland Oy

72. Export/Import
© Miracle Finland Oy

73. © Miracle Finland Oy

74. © Miracle Finland Oy

75. Reporting
© Miracle Finland Oy

76. © Miracle Finland Oy

77. © Miracle Finland Oy

78. © Miracle Finland Oy

79. © Miracle Finland Oy

80. © Miracle Finland Oy

81. Notation
© Miracle Finland Oy

82. © Miracle Finland Oy

83. Domains administration
© Miracle Finland Oy

84. © Miracle Finland Oy

85. © Miracle Finland Oy

86. © Miracle Finland Oy

87. © Miracle Finland Oy

88. Types Administration
© Miracle Finland Oy

89. © Miracle Finland Oy

90. Design Rules
© Miracle Finland Oy

91. © Miracle Finland Oy

92. © Miracle Finland Oy

93. Compare/merge models
© Miracle Finland Oy

94. Synchronize Model with Data
Dictionary
© Miracle Finland Oy

95. Synchronize Data Dictionary with
Model
© Miracle Finland Oy

96. Preferences
© Miracle Finland Oy

97. © Miracle Finland Oy

98. © Miracle Finland Oy

99. © Miracle Finland Oy

100. © Miracle Finland Oy

101. © Miracle Finland Oy

102. © Miracle Finland Oy

103. © Miracle Finland Oy

104. © Miracle Finland Oy

105. © Miracle Finland Oy

106. Version control (Subversion)
© Miracle Finland Oy

107. © Miracle Finland Oy

108. © Miracle Finland Oy

109. © Miracle Finland Oy

110. © Miracle Finland Oy

111. © Miracle Finland Oy

112. Data Modeler and agile
Requirement analysis (Logical, ER: main concepts)
Conceptual design (Logical, ER: the big picture)
Logical design (Logical ER: iteration 1-n, Relational
iteration 1-n)
Physical design (Relational iteration 1-n, Physical
iteration 1-n, DLLs 1-n iteration)
© Miracle Finland Oy

113. © Miracle Finland Oy © Miracle Finland Oy

114. Conclusions
• To see the datastructures in the database and
to maintain the data: SQL Developer
• To design the database and to maintain the
data structures: Data Modeler
• To design the data architecture: Data Modeler
© Miracle Finland Oy

115. Conclusions
• Data Modeler is a good tool; good support for
iterative processes
• Enables documenting and versioning (and
comparing the versions)
• Enables multiuser environment
• Is free to use
• Support for other databases as well
• I see no reason not to use it!
© Miracle Finland Oy

116. OTN
• http://www.oracle.com/technetwork/develop
er-tools/sql-developer/learnmore/index.html
• http://www.oracle.com/technetwork/develop
er-tools/datamodeler/learnmore/index.html
© Miracle Finland Oy

117. Self study, Oracle Learning Library
SQL Developer Data Modeler Release 3.1 Self
Study - All Demos
http://apex.oracle.com/pls/apex/f?p=44785:24:
1368386639082001::NO:24:P24_CONTENT_ID
,P24_PREV_PAGE:5966,2
© Miracle Finland Oy

118. Self study, Oracle Learning Library
• Re-engineering Your Database Using Oracle
SQL Developer Data Modeler 3.1
• http://apex.oracle.com/pls/apex/f?p=44785:2
4:11524540948794::NO:24:P24_CONTENT_ID,
P24_PREV_PAGE:6266,2
• Etc.
© Miracle Finland Oy

119. Users Guide
• http://docs.oracle.com/cd/E29463_01/doc.33
/e35120.pdf
• http://docs.oracle.com/cd/E29463_01/doc.33
/e35120/toc.htm
(April 2013)
© Miracle Finland Oy

120. Thank You!
Questions?
heli@miracleoy.fi
Also known as helifromfinland
© Miracle Finland Oy