Database Foundations. 5-1 Mapping Entities and Attributes. Copyright 2015, Oracle and/or its affiliates. All rights reserved.

Size: px

Start display at page:

Bennett Rice
5 years ago
Views:

2 Database Foundations 5-1

3 Road Map You are here Mapping Entities and Attributes Mapping Primary and Foreign Keys 3

4 Objectives This lesson covers the following objectives: Describe why you need to create a relational model Explain the naming conventions used in a relational database 4

Glossary Name abbreviations Design rules Custom rules

5 Objectives This lesson covers the following objectives: Use Oracle SQL Developer Data Modeler to apply naming standards by creating: Glossary Name abbreviations Design rules Custom rules Transformations Map simple entities to tables Map attributes to column names 5

Can be used as the basis for implementing any type of

6 Need for Creating a Relational Model A relational model: Is the blue print for the actual database implementation Can be used as the basis for implementing any type of DBMS. The ideal model can be adapted to an RDBMS model. 6

7 Transformation Process: Logical to Relational Model Logical Model Transformation Relational Model 7

Hayes Drive 08-12-53 20 134 Gonzales 5609 Maple Court 10-02-87 40 Primary

8 Tables: A Recap Table: EMPLOYEES Columns ID Name Address Birth_date Department_ID 110 Jones 12 Oxford Street Rows 301 Smith 53 Hayes Drive Gonzales 5609 Maple Court Primary key column Foreign key column to the DEPARTMENTS table Table in the relational model 8

9 Terminology Mapping: A Recap ANALYSIS Logical model Entity Attribute Primary UID Secondary UID Relationship Business constraints DESIGN Relational model Table Column Primary key Unique constraint Foreign key Check constraints 9

10 Naming Conventions Decide on conventions for: Table names Column names and special characters (%, *, #, -, space, ) Table short names (abbreviations) 10

11 Naming Conventions Decide on conventions for: Primary and unique key constraint names Foreign key constraint names Foreign key column names Check constraints 11

12 Naming Restrictions with Oracle Database Table and column names: Must start with a letter May contain up to 30 alphanumeric characters Must not contain spaces or some special characters Must avoid reserved words Table names must be unique within a schema. Column names must be unique within a table. 12

13 Applying Naming Standards Using Oracle SQL Developer Data Modeler Glossary Logical Model Name Translation Naming Templates Relational Model Name Formatter Naming Restrictions Design Rule Validation 13

14 Glossary Creating a Glossary from a Logical Model 14

15 Glossary Editor 15

16 Glossary Editor 16

17 Name Abbreviations Example of a.csv file content 17

18 Executing Design Rules a b 18

19 Creating Rule Sets for Design Rules b a c 19

20 Custom Design Rules and Transformation 20

21 Custom Design Rules and Transformation 21

22 Case Scenario: Design Rules Let me see if the ERD for the Simplified Library Management System is complying with the database design rules. If the ERD is not complying with the design rules, can I fix it? 22

23 Case Scenario: Applying Design Rules a b c The warning is fixed, and now the design is OK. 23

24 Mapping Simple Entities to Tables Entities Tables 24

25 Naming Entities a b c 25

26 Engineering Entities 26

27 Mapping Attributes to Columns Entities Tables 27

28 Mapping Attributes to Columns: Column Names 28

29 Engineering Attributes 29

30 Reviewing the Glossary 30

31 Adding the Glossary as the Naming Standard a b c 31

32 Mapping Attributes to Columns with the Glossary Entities Tables After Glossary Is Applied 32

33 Applying Name Abbreviations a c b 33

34 Summary In this lesson, you should have learned how to: Describe why you need to create a relational model Explain the naming conventions used in a relational database 34

35 Summary In this lesson, you should have learned how to: Use Oracle SQL Developer Data Modeler to apply naming standards by creating: Glossary Name abbreviations Design rules Custom rules Transformations Map simple entities to tables Map attributes to column names 35

Database Design. 9-2 Basic Mapping: The Transformation Process. Copyright 2015, Oracle and/or its affiliates. All rights reserved.

Database Design. 9-2 Basic Mapping: The Transformation Process. Copyright 2015, Oracle and/or its affiliates. All rights reserved. Database Design 9-2 Objectives This lesson covers the following objectives: Distinguish between a conceptual model and a physical model Apply terminology mapping between the two models Understand and apply