Second Normal Form - Buisness Management - Lecture Slides, Slides of Business Administration

Business Management is one of the most important subject in Management Sciences.Following are the key points discussed in these Lecture Slides : Second Normal Form, Functional Dependency, Uniquely Associated, Transitive Dependencies, Eliminate Deletion, Beyond Data Modeling, Optimised Model, Resilience, Constraints of The System, Realistic Constraints

Typology: Slides

2012/2013

Uploaded on 07/29/2013

devsena
devsena 🇮🇳

4.5

(14)

134 documents

1 / 11

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Second Normal Form
Record must be in first normal form first
each item in the record must be fully
dependent on the key for identification
Functional dependency means a data
item’s value is uniquely associated with
another’s
only on-to-one relationship between
elements in the same file
otherwise split into more tables
Docsity.com
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download Second Normal Form - Buisness Management - Lecture Slides and more Slides Business Administration in PDF only on Docsity!

Second Normal Form

  • Record must be in first normal form first
  • each item in the record must be fully

dependent on the key for identification

  • Functional dependency means a data

item’s value is uniquely associated with another’s

  • only on-to-one relationship between

elements in the same file

  • otherwise split into more tables

Third normal form

  • to remove transitive dependencies
  • when one item is dependent on an item

which is dependent from the key in the file

  • relationship is split to avoid data being lost

inadvertently

  • this will give greater flexibility for the design

of the application + eliminate deletion problems

  • in practice, 3 NF not used all the time -

speed of retrieval can be affected

Realistic constraints

  • Users cannot cope with too many tables
  • Too much development required in hiding

complex data structure

  • Too much administration
  • Optimisation is impossible with too many

tables

  • Actually: RDBs can be quite slow!

Key practical questions

  • What are the most important tasks that the

DB MUST accomplish efficiently?

  • How must the DB be rigged physically to

address these?

  • What coding practices will keep the coding

clean and simple?

  • What additional demands arise from the

need for resilience and security?

4 way trade-off

Performance

Clarity of code

Ease of use

Security

Key decisions

  • Oracle offers many different ways to do things
    • Indexes
    • Backups…
  • Good analysis is not only about knowing these => understanding whether they are appropriate
  • Failure to think it through => unworkable model
  • Particularly, predicting performance must be done properly - Ok on the technical side, tricky on the business side

Using scenarios for analysis

  • Define standard situation for DB use
  • Analyse their specific requirements
  • Understand the implications for DB design
  • Compare and contrast new problems with

old ones

Categories of critical operations

  • Manual transaction processing = complex DE by small number of operators
  • Automatic transaction processing: large number of concurrent users performing simple DE
  • High batch throughput: automatic batch input into DB of very large number of complex transactions
  • Data warehousing: large volumes of new data thrown on top every day at fixed intervals + intensive querying