Discover millions of ebooks, audiobooks, and so much more with a free trial

Only $9.99/month after trial. Cancel anytime.

Oracle Quick Guides: Part 2 - Oracle Database Design
Oracle Quick Guides: Part 2 - Oracle Database Design
Oracle Quick Guides: Part 2 - Oracle Database Design
Ebook132 pages1 hour

Oracle Quick Guides: Part 2 - Oracle Database Design

Rating: 0 out of 5 stars

()

Read preview

About this ebook

This is Part 2 of a series of quick learning guides for Oracle designers, developers and managers. Part 2 introduces completely new entrants to concepts of Oracle database analysis and design, database normalisation, the logical datamodel, E-R modelling and diagrams, logical to physical transformation in Oracle Designer, physical database design, de-normalization, database design for performance, and building a physical database from a server model.

These guides are designed to rapidly deliver key information about Oracle to the following audience groups:

- Project Managers and Team Leaders who are new to Oracle and need rapid access to strategic information about the Oracle design and development environment.

- Business Analysts, Designers and Software developers who are new to Oracle and need to make first steps in gaining a detailed understanding of the design and development issues involved in Oracle.

Part 2 assumes that the reader has a basic knowledge of the relational model and a basic understanding of logical and physical design concepts. The contents of Part 2 include the following subject headings:

Preface and Audience
1. The Analysis phase - Separating Functional and Database Design
2. Introduction to Datamodelling and Database Design: Logical and Physical concepts of design
3. Practical Logical Design - Data-modelling
4. Practical Logical Design using Oracle Designer
5. Moving from the Logical to the Physical design
6. Practical Physical Design (using Oracle Designer)
7. Designing a database for Performance
8. Building the physical database from Designer
9. Managing Changes during development
10. Glossary of Terms

LanguageEnglish
Release dateMay 13, 2013
ISBN9788494085352
Oracle Quick Guides: Part 2 - Oracle Database Design
Author

Malcolm Coxall

Malcolm Coxall is a management consultant, systems analyst, organic farmer and author, with more than 30 years experience working for many of the world's largest corporate and institutional organisations, starting in the field of dispute arbitration for the ILO. These experiences have provided him a ringside view of the management methodologies used by medium and large businesses in areas as diverse as banking, oil, defence, telecoms, insurance, manufacturing, mining, food, agriculture, aerospace, textiles, and heavy engineering. Malcolm has published articles on political science, sociology, human design, sustainable agriculture, organic food production, technology in organic farming, biodiversity, forest management, environmental protection and environmental economics. He is active in European environmental politics and was a successful private complainant in the European Court of Justice in several cases of national breaches of European environmental law. He now lives in Southern Spain from where he continues his IT and system consultancy work, writing and managing the family's organic olive farm.

Read more from Malcolm Coxall

Related to Oracle Quick Guides

Titles in the series (4)

View More

Related ebooks

Data Modeling & Design For You

View More

Related articles

Reviews for Oracle Quick Guides

Rating: 0 out of 5 stars
0 ratings

0 ratings0 reviews

What did you think?

Tap to rate

Review must be at least 10 words

    Book preview

    Oracle Quick Guides - Malcolm Coxall

    Oracle Quick Guides Part 2 - Oracle Database Design

    Oracle Quick Guides - Part 2 Oracle Database D esign

    Malcolm Coxall

    Edited by Guy Caswell

    Published by M.Coxall - Cornelio Books

    Copyright 2013 Malcolm Coxall

    First Published in Spain , United Kingdom 2013

    ISBN: 978-84-940853-5-2

    "Space does not exist unless there are objects in it

    Nor does time exist without events."

    Contents

    Preface a nd A u dience .

    1. The A n alysis phase - Sep a rating F u nctional and Database Design .

    2. Introduction to Data modelling and Database Design

    3. Practical Logical Design - Data modelling

    4. Practical Logical Design using Oracle Designer .

    5. Moving from the Logical to the Physical design.

    6. Practical Physical Design using Oracle Designer.

    7. Designing a database for Performance.

    8. Building the physical database from Oracle Designer.

    9. Managing Changes during development.

    10. Glossary of Terms.

    About the Author

    Preface and Audience

    Oracle Quick Guides: Welcome to Oracle Quick Guides, a series of quick learning guides for Oracle designers, developers and managers.

    Guide Audience: These guides are designed to rapidly deliver key information about Oracle to the following audience groups :

    - Project Managers, Team Leaders and Testers who are new to Oracle and need rapid access to strategic information about the Oracle development environment.

    - Business Analysts, Designers and Software D evelopers who are new to Oracle and need to make a first step in gaining a detailed understanding of the design and development issues involved in Oracle.

    Guide Content s : These guides have been divided by subject matter . They become increasingly complex and more specific the later the volume . Thus, volume 1 is quite general but later volumes are very technical and specific.

    Our Objective: There are plenty of Oracle textbooks on the market. Most of them are huge and only partly relevant to a particular group of readers. Therefore, we decided to divide the subject into smaller, more targeted volumes in order that you only get the information YOU need.

    For example, a Project Manager doesn't need to know some of the more esoteric programming tips , but will need to know some of the strategic issues affecting design and testing. In a similar way, a Programmer is much more interested in the syntactic details than in the strategic issues affecting the choice of an Oracle upgrade path.

    And so we target these guides at particular groups with specific interests and we try to avoid overloading the reader with too much detail or extraneous material.

    Assumptions: We assume that the reader will be using Oracle 9i, 10g or 11g, Oracle Designer 10g, and employing a standard RAD development methodology.

    ---o0o---

    1. The Analysis phase - Separating Fu nc tional and Database Design

    The first step in Oracle RDBMS system analysis and design is establishing the separation between Database d esign and Function al (s oftware) design. This needs to be done with some care because , in an Oracle database, many elements of data validation and execution occur at the database level rather than in a piece of external software code. This is a fundamental difference between tradition al 3G software developments and the design and development in an Object Relational environment , like Oracle.

    Oracle is a so-called Object Relational database and this means that much default validation behaviour is actually embedded in the database itself. A design team lead er needs to constantly decide the appropriate place for software code to reside and execute , i.e. in the database as a trigger or as a piece of ex ternal code executed on demand against the database.

    Generally, the rule is that as much code as possible is associated with the tables within the database when the code is considered to have a low volatility ( i.e. the software functionality hardly ever changes). Software which is more volatile and prone to change is generally excluded from being embedded at the database level.

    Logically, software embedded in the database tends to represent those immutable properties which define the business rules inherent in the database object itself. For example, it would be illogical if an order number was not unique in a database : order numbers are unique; otherwise an order cannot be identified.

    Therefore , the concept of guaranteeing unique order numbers in the ORDERS table is a good candidate to become part of the ORDERS inherent validation, rather than being guaranteed by some piece of external software every time an order is added, because t his validation is an inherent and unchangeable part of an order.

    This separation of validation and other processing between database object and external software complicates the designer's life somewhat and as a consequence, the design team lead must separate the tasks of Design and Development between the roles of database design and functional design. This also means dividing up the project into a Database Design Team and an Application (functional) development team. And it also means that the two teams need to liaise closely on where particular software functionality will reside.

    T his normally means that the Database Design Team need to start their Analysis and Logical design work well ahead of the Application (functional) development team , because the A pplication (functional) designers need to have a stable database design in place before even considering software design definitions and certainly long before any code is produced .

    Here is a simplified organisation chart which indicates how roles are split between Oracle database designers and Oracle software developers:

    Since t he purpose of this guide is to examine Database Design , we will leave functional issues for now . This is the subject of a nother Oracle Quick G uide , where we will consider the issues involved in logical and physical software design from Functional analysis to physical software module design and definition. For now , we will focus on the logical and physical design of an underlying Oracle database from Analysis, through Logical data modelling to Physical Database rollout.

    2. Introduction to Data modelling and Database Design

    Logical and Physical concepts of design :

    2.1 Introduction: There are two clear steps involved in moving from a Business a nalysis stage to a p hysical database . Step 1 is Logical Design and Step 2 is Physical Design. Step 1 may be by-passed in some cases.

    Step 1 is optional in those cases where the logical relationships are so self-evident and well- known to the designers. In such a case , a design team may choose to skip l ogical database d esign and move directly to the physical database d esign. This is not an uncommon strategy and can save a lot of time. However, if the application is in new territory for the users and the developers , and where little is known about the data and its relationships, it is important to go through the process of formal logical design together with the business users. In database design, late-breaking design changes and surprises can carry ve ry high costs. So it generally pays off to err on the side of more logical design time with the users , rather than less.

    Step 1: Logical Design:

    - A Logical database design is the output from a data a nalysis process , together with selected users .

    - The process of data analysis is generally carried out based on an initial User Requirements D efinition. During this process, a business analyst establishes the core business entities and relationships based on interviews with key business users.

    - A fully- fledged technically accurate logical data

    Enjoying the preview?
    Page 1 of 1