Understanding Database Processing: Databases, Data Models, and Normalization, Study notes of Accounting

This chapter explores the concept of databases, explaining what they are and their purpose. We delve into the idea of a self-describing collection of integrated records, discussing bytes, columns, records, tables, and relationships. Furthermore, we discuss data models, their role in database development, and the entity-relationship data model. We also cover normalization, a process of converting poorly structured tables into well-structured ones, and data integrity problems.

Typology: Study notes

Pre 2010

Uploaded on 11/11/2009

ac062
ac062 🇺🇸

8 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Chapter 5 ACIS
Database Processing
1. What is the purpose of a database?
-to keep track of things
-lists that involve single theme: spreadsheet
-lists that involve multiple themes: database
2. What is a database?
Database: self-describing collection of integrated records
Byte: character of data
- Bytes grouped into columns
oColumns grouped into rows called records
Group of rows or records is called table or file
Database is collection of tables plus relationships among rows in those tables plus special data, called
metadata, that describes structure of the database
- What are relationships among rows?
oKeys : column or group of columns that identifies a unique row in a table
oForeign key : columns which are keys of a different (foreign) table than the one in which
it resides
oRelational database : databases that carry their data in the form of tables and represent
relationships using foreign keys
- Metadata : data that describe data
- Enterprise DBMS vs Personal DBMS
oEnterprise DBMS products process large organizational and workgroup databases
24/7 operations
Can manage databases that span dozens of different magnetic disks with
hundreds of gigabytes or more data
oPersonal DBMS products designed for smaller, simpler database applications
Fewer than 100 users, normally single
Ex: student database
3. How are data models used for database development?
Data Model: describes data and relationships that will be stored in the database; like a blueprint
Entity-relationship data model: tool for constructing data models
- Describes content of a data model by defining the entities stored in the database and the
relationships among those entities
Unified Modeling Language (UML): less popular tool for data modeling
Entity: some thing that users want to track
- Ex: order, customer, item
oSome represent physical object (item or customer), others represent logical construct or
transaction (order or contract)
pf2

Partial preview of the text

Download Understanding Database Processing: Databases, Data Models, and Normalization and more Study notes Accounting in PDF only on Docsity!

Chapter 5 ACIS Database Processing

  1. What is the purpose of a database? -to keep track of things -lists that involve single theme: spreadsheet -lists that involve multiple themes: database
  2. What is a database? Database: self-describing collection of integrated records Byte: character of data
    • Bytes grouped into columns o Columns grouped into rows called records  Group of rows or records is called table or file Database is collection of tables plus relationships among rows in those tables plus special data, called metadata, that describes structure of the database
    • What are relationships among rows? o Keys: column or group of columns that identifies a unique row in a table o Foreign key: columns which are keys of a different (foreign) table than the one in which it resides o Relational database: databases that carry their data in the form of tables and represent relationships using foreign keys
    • Metadata: data that describe data
    • Enterprise DBMS vs Personal DBMS o Enterprise DBMS products process large organizational and workgroup databases  24/7 operations  Can manage databases that span dozens of different magnetic disks with hundreds of gigabytes or more data o Personal DBMS products designed for smaller, simpler database applications  Fewer than 100 users, normally single  Ex: student database
  3. How are data models used for database development? Data Model: describes data and relationships that will be stored in the database; like a blueprint Entity-relationship data model: tool for constructing data models
    • Describes content of a data model by defining the entities stored in the database and the relationships among those entities Unified Modeling Language (UML): less popular tool for data modeling Entity: some thing that users want to track
    • Ex: order, customer, item o Some represent physical object (item or customer), others represent logical construct or transaction (order or contract)

o Always singular  Attributes: describe characteristics of the entity  Identifier: attribute (or group of) whose value associated with one and only one entity instance  Ex: OrderNumber identifier of order because only one order instance has given value of ordernumber Relationships: entities have relationships to each other Crow’s feet: little lines which are shorthand for the multiple lines between entities which are related 1:N: one to many: relationships in which one entity to many entities N:M: many to many Normalization: process of converting a poorly structured table into 2 or more well-structured tables Data Integrity Problems: not all aspects of table are correct

  • Only occurs if data are duplicated o Fix by eliminated the duplicated data Normalizing for data integrity
  • General goal of normalization: construct tables so that every table has single topic or theme o Database practitioners classify tables into various normal forms according to the kinds of problems they have o “those tables not normalized”=the tables have format that could cause data integrity problems
  • Normalization just one criterion for evaluating database designs
  • Slower to process Representing relationships Transforming data model into relation database design:
  1. database designer creates table for each entity
  • identifier becomes key of table
  • attributes become columns
  1. resulting tables normalized so that each table has single theme
  2. represent relationship among those tables
  3. What is the users’ role in development of databases? Database: model of how users view their business world
  • Easiest time to change structure during data modeling stage