Database Training

OVERVIEW OF DATABASE
SYSTEM
1
CMS Computers Ltd. © Copyright 2007 Quality Driven Leadership 1
Topics
What is a Database System?
What is a Database?
Why Database?
Data Independence
Relational Systems, and Others
2
3
Introduction to Database
Data stored in file systems – problems with
: redundancy
: maintenance
: security
: efficient access to the data
Database Management Systems
Software tools that enable the management
(definition, creation, maintenance and use) of large
amounts of interrelated data stored in a
computer accessible media. 4
Capabilities of Database
Management System
 Manage persistent data
 Access large amounts of data efficiently
 Support for at least one data model
 Support for certain high-level language that allow the user to
define the structure of the data, access data, and manipulate
data
 Transaction management – the capability to provide correct,
concurrent access to the database by many users at once
 Access control – the ability to limit access to data by
unauthorized
users, and the ability to check the validity of data
 Resiliency – the ability to recover from system failures without
losing data
5
Design Phases
Difficulties in designing the DB’s effectively
brought design methodologies based on data
models
 Database development process
Business Information Requireme
Conceptual Design
Produces the initial model of the Conceptual Data
real world in a conceptual model Modeling
Logical Design
Consists of transforming the Logical
conceptual schema into the data Database
model supported by the DBMS Design
Physical Design Physical
Aims at improving the Database
performance of the final system Design
6
Conceptual Design
The process of constructing a model of the
information used in an enterprise
Is a conceptual representation of the data

structures
Is independent of all physical considerations
Should be simple enough to communicate with the

end user
Should be detailed enough to create the physical

structure
Business information Conceptual model
requirements
Conceptual Design (Entity-Relationship Model)
7
Entity Relationship Model
The Entity-Relationship model (ER) is the most common conceptual
model for database design nowadays
No attention to efficiency or physical database design
Describes data as entities, attributes, and relationships
It is assumed that the Entity-Relationship diagram will be turned into

one of the other available models during the logical design
Entity-relationship
model
Hierarchical Network model

model
Relational model
8
Entity
A thing of significance about which the business needs to store
information
trivial example: employee, department
CERN controls example: controls_entity, location, entity_parameter,
system, quantity_code, data_type
Entity instance – an individual occurrence of a given entity
trivial example: a single employee

CERN controls example: a given system (e.g. SPS Vacuum)
Note: Be careful when establishing the ‘boundaries’ for the entity, e.g.
entity employee – all employees in the company or all employees in
a given department – depends on the requirements
9
Attributes
Attributes are properties which describe the entity
attributes of system - id, description, comments
Attributes associate with each instance of an entity a value from a

domain of values for that attribute
set of integers, real numbers, character strings
• Attributes can be SYSTEM

: optional # id
: mandatory * description
o comments
• A key - an attribute or a set of
attributes,
whose values uniquely identify each
instance of a given entity 10
Relationships
Associations between entities
examples: employees are assigned to departments
entity_parameters are generated by systems
Degree - number of entities associated with a relationship (most

common case - binary)
Cardinality - indicates the maximum possible number of entity

occurrences
Existence - indicates the minimum number of entity occurrences

set of integers, real numbers, character strings
: mandatory
: optional
ENTITY_PARAMETER
SYSTEM produces # id
# id * description
is
* description generated
o expert_name
by ……
11
Database System
Computerized record-keeping system
Supports operations
Add or delete files to the database
Insert, retrieve, remove, or change data in
database
Components
Data, hardware, software, users
12
Database System - Data
May support single or many users
Many users in organizations
Data is integrated
Data is shared
Different users will require different views
13
Database System - Hardware
Data is stored on Disk
Direct access to subset portions
Rapid I/O
Data operated on in main memory
14
Database System - Software
Database manager
Database server
Database management system (DBMS)
DBMS provided by specific vendor
15
Database System - Software
DBMS is not ( but may come with)
Application Development Tools
Application Software
TP Monitor
Report Writer
System utilities
16
Database System - Users
Application programmers
End users
Database Administrators
17
What is a Database?
Collection of persistent data
Collection of true propositions
Made up of entities, relationships, properties
Implements a data model
18
What is a Database? – Entities
and Relationships
Entity is a person, place, event or thing,
about which we wish to store information
Relationship is a connection between
entities, about which we wish to store
information
A relationship can be considered a special
case of entity
19
What is a Database? -
Properties
Entities have properties
Properties are the characteristics of an entity
Properties can be simple or complex
20
Data and Data Models
Database is a collection of true propositions
Data model is an abstract, self-contained,
logical representation
Implementation of the data model on a
specific platform
Data model as template vs. instantiation for
a specific enterprise
21
Why Database?
Shared data
Reduced redundancy
Reduced inconsistent data
Transaction support
Support for data integrity
Security enforcement
Support for standards
Conflicting requirements can be met
22
Data Independence
Database separates logical and physical
representation of data
Allows changes to application programs
without changing the structure of the
underlying data and vice versa
23
Materialized Data
Stored fields, collected as…
Stored records, collected as…
Stored files
Old systems, e.g., COBOL applications,
directly connect to data formats
Newer database systems offer greater data
independence, but could do better
24
Relational Systems
Most important innovation in database
history
Based on logic and mathematics
Data is perceived as tables, only
Operators derive new tables from existing
A table is a “relation,” mathematically
Not pointer based (to the user)
25
The Relational Model –
Informally
Structural
oData is perceived by users as tables
Integrity
oData subject to specific integrity requirements
Manipulation
oOperators derive tables from other tables
•Restrict
•Project
•Join
26
The Relational Model –
Informally
Structural
Data is perceived by users as tables
Integrity
Data subject to specific integrity requirements
Manipulation
Operators derive tables from other tables
Restrict
Project
Join
27
Type of Databse
Oracle
MS SQL(Microsoft)
MY SQL
ACCESS (Microsoft)
SYBASE
DB2(IBM)
XML
28
Oracle Database Support
Failsafe over
RAC
Standalone
29

Database Training

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Database Training

Enviado por

Direitos autorais:

Formatos disponíveis

OVERVIEW OF DATABASE

Is a conceptual representation of the data

Is independent of all physical considerations

Should be simple enough to communicate with the

Should be detailed enough to create the physical

No attention to efficiency or physical database design

Describes data as entities, attributes, and relationships

It is assumed that the Entity-Relationship diagram will be turned into

Hierarchical Network model

trivial example: a single employee

Attributes associate with each instance of an entity a value from a

• Attributes can be SYSTEM

Degree - number of entities associated with a relationship (most

Cardinality - indicates the maximum possible number of entity

Existence - indicates the minimum number of entity occurrences

Você também pode gostar