Scribd
Upload
59 views3 pages

Ais CH4

Databases consolidate data from separate files into a centralized pool to serve various users and applications. A relational database organizes data into tables with rows and columns, where each row represents a record and each column represents an attribute. Designing a normalized relational database avoids data inconsistencies by eliminating redundant data storage and defining relationships between tables using primary and foreign keys. Semantic data modeling uses knowledge of business processes to efficiently design databases that meet users' needs.

Uploaded by

Divine Grace Bravo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
59 views3 pages

Ais CH4

Databases consolidate data from separate files into a centralized pool to serve various users and applications. A relational database organizes data into tables with rows and columns, where each row represents a record and each column represents an attribute. Designing a normalized relational database avoids data inconsistencies by eliminating redundant data storage and defining relationships between tables using primary and foreign keys. Semantic data modeling uses knowledge of business processes to efficiently design databases that meet users' needs.

Uploaded by

Divine Grace Bravo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

CH4 RELATIONAL DATABASES

Files versus Databases


Database - A set of interrelated, centrally coordinated data files that are stored with as little data redundancy as
possible.
- consolidates records previously stored in separate files into a common pool and serves a variety
of users and data processing applications

DATA HIERARCHY
 Field – attributes about an entity
 Record – related group of fields

Using Data Warehouses for Business Intelligence


 data warehouse - Very large databases containing detailed and summarized data for a number of years that
are used for analysis rather than transaction processing (usually updated periodically rather than in real
time)
- do not replace transaction processing databases; they complement them by providing
support for strategic decision making
 business intelligence - Analyzing large amounts of data for strategic decision making
 online analytical processing (OLAP) - Using queries to investigate hypothesized relationships among data.
 data mining - Using sophisticated statistical analysis to “discover” unhypothesized relationships in the
data.
 Data validation controls are needed to ensure that data warehouse input is accurate.
 Verifying the accuracy, called scrubbing the data, is often one of the most time-consuming and expensive
steps in creating a data warehouse

Advantages of Database Systems


 Data Integration – files are logically combined and made accessible to various systems
- Master files are combined into large “pools” of data that many application programs access.
 Data Sharing – data in one place is more easily accesses by authorized users
 Minimizing Redundancy and Data Inconsistency – eliminates the same data being stored in multiple
files, thus reducing inconsistency in multiple versions of the same data.
 Data Independence – data is separate for the programs that access it. Each can be changed without
changing the other
 Cross-functional analysis - In a database system, relationships, such as the association between selling
costs and promotional campaigns, can be explicitly defined and used in the preparation of management
reports

DATABASE TERMINOLOGY
 Database management Systems - The program that manages and controls the data and the interfaces
between the data and the application programs that use the data stored in the database.
 database administrator - The person responsible for coordinating, controlling, and managing the database
 database system - The data base, the DBMS, and the application programs that access the database through
the DBMS.

DATABASE SYSTEMS
o record layout - Document that shows the items stored in a file, including the order and length of the data fields
and the type of data stored.
Logical vs Physical
 Physical - The way data are physically arranged
and stored in the computer system.  logical view - How people conceptually organize,
- Depends on explicitly knowing: view, and understand the relationships among data
o How the data actually items.

Schemas
 schema - A description of the data elements in a database, the relationships among them, and the logical
model used to organize and describe the data
- Three Levels:
1. conceptual-level schema - The organization-wide view of the entire database that lists all data
elements and the relationships between them.
2. external-level schema - An individual user’s view of
portions of a database;
- also called a subschema (A subset
of the schema; the way the user
defines the data and the data
relationships.)
3. internal-level schema - A low-level view of the entire
database describing how the data are actually stored and
accessed.

Data Dictionary
- Information about the structure of the database, including a
description of each data element

DBMS Languages
 Data Definition Language (DDL)
DBMS language that builds the data dictionary, creates the database,
describes logical views, and specifies record or field security constraints
 data manipulation language (DML)
DBMS language that changes database content, including data element
creations, updates, insertions, and deletions.
 data query language (DQL)
High-level, English-like, DBMS language that contains powerful, easy-to-
use commands that enable users to retrieve, sort, order, and display data
 report writer - DBMS language that simplifies report creation.

RELATIONAL DATABASES
 data model - An abstract representation of database contents.
 relational data model - A two-dimensional table representation of data;
- each row represents a unique entity (record) and each column is a field where record attributes are
stored.
 tuple - A row in a table that contains data about a specific item in a database table.

Types of Attributes
 primary key - Database attribute, or combination of attributes, that uniquely identifies each row in a table.
 foreign key - An attribute in a table that is also a primary key in another table;
- used to link the two tables

Designing a Relational Database


1. Designing a Relational Database
 update anomaly - Improper database organization where a non-primary key item is stored
multiple times; updating the item in one location and not the others causes data inconsistencies.
 insert anomaly - Improper database organization that results in the inability to add records to a
database.
 delete anomaly - Improper organization of a database that results in the loss of all information
about an entity when a row is deleted.
2. Vary the Number of Columns.
3. The Solution: A Set of Tables.
 relational database - A database built using the relational data model.

Basic Requirements of a Relational Database


1. Every column in a row must be single valued
2. Primary keys cannot be null
 entity integrity rule - A non-null primary key ensures that every row in a table represents
something and that it can be identified
3. Foreign keys, if not null, must have values that correspond to the value of a primary key in another
table.
 referential integrity rule - Foreign keys which link rows in one table to rows in another
table must have values that correspond to the value of a primary key in another table.
4. All non-key attributes in a table must describe a characteristic of the object identified by the
primary key

Two Approaches to Database Design


1. normalization - Following relational database creation rules to design a relational database that is free from
delete, insert, and update anomalies.
- begins by assuming that everything is initially stored in one large table
- third normal form (3NF) - a set of tables free of update, insert, and delete anomalies
2. semantic data modeling - Using knowledge of business processes and information needs to create a diagram
that shows what to include in a fully normalized database (in 3NF)
- significant advantages.
1. First, using a system designer’s knowledge of business processes facilitates the efficient
design of transaction processing databases.
2. Second, the graphical model explicitly represents the organization’s business processes and
policies and, by facilitating communication with system users, helps ensure that the new
system meets users’ actual needs
Query

You might also like