Professional Documents
Culture Documents
Using
Microsoft SQL Server Admas University
I.C.T Departments
Semestre 2
DATABASE MANAGEMENT
SYSTEMS (DBMS I)
CHAPTER 01
INTRODUCTION
TO DBMS
DATABASE MANAGEMENT
SYSTEMS (DBMS I)
All these products are used for a specific purpose that can be
associated with a specific user whose job is to do a specific task. This
means that it is possible to designate one or more database
administrators who may control the DATABSE.
DATABASE ADMINISTRATOR:
1. He is the person who is responsible for controlling the entire
DATABASE components (Such as Different databases, tables,
relationships, database backups, database restoration....etc).
FOR EXAMPLE: A customer database, may have columns for the customer's
ID, first name, last name, and email address, and each row contains an
individual customers data.
DATABASE MANAGEMENT SYSTEMS (DBMS I)
Users can interact with a database management system through software
applications that include programming code to work with the database.
These software applications can USE VISUAL STUDIO or OTHER
PACKAGES.
DATABASE MANAGEMENT SYSTEMS (DBMS I)
DATABASE MANAGEMENT SYSTEMS (DBMS I)
DATABASE MANAGEMENT SYSTEMS (DBMS I)
DATABASE MANAGEMENT SYSTEMS (DBMS I)
DATABASE MANAGEMENT SYSTEMS (DBMS I)
Primary Key: DBMS use primary keys for retrieving data specifically.
Primary Key Definition: A primary key identifies & represents one
particular FIELD of a Line or Record which is unique value for that
Record or Line. A Primary Key is assigned to the field that is unique for
that Line of data.
For Example: In an employee table the primary key may be an
employee identification number (employee ID) that each employee is
permanently assigned to and which no other employee will use.
Program-Data Dependence
All programs maintain metadata for each file they use
Duplication of Data
Different systems/programs have separate copies of the same data
Limited Data Sharing
No centralized control of data
Lengthy Development Times
Programmers must design their own file formats
Excessive Program Maintenance
80% of information systems budget
27
Problems with Data Dependency
29
Problems with Data Redundancy
30
SOLUTION:
The DATABASE Approach
31
Database Management System
A software system that is used to create, maintain, and
provide controlled access to user databases
Order Filing
System
1. Program-data independence
2. Planned data redundancy
3. Improved data consistency
4. Improved data sharing
5. Increased application development productivity
6. Enforcement of standards
7. Improved data quality
8. Improved data accessibility and responsiveness
9. Reduced program maintenance
10. Improved decision support
33
Costs and Risks of the Database Approach
34
Elements of the Database Approach
Data models
Graphical system capturing nature and relationship of data
Enterprise Data Modelhigh-level entities and relationships for
the organization
Project Data Modelmore detailed view, matching data structure
in database or data warehouse
Relational Databases
Database technology involving tables (relations) representing
entities and primary/foreign keys representing relationships
Use of Internet Technology
Networks and telecommunications, distributed databases,
client-server, and 3-tier architectures
Database Applications
Application programs used to perform database activities
(create, read, update, and delete) for database users
35
Components of the Database Environment
1. Personal databases
2. Workgroup databases
3. Departmental/divisional databases
4. Enterprise database
37
38
Figure 1-6
Typical data
from a
personal
database
39
Figure 1-7 Workgroup database with wireless
local area network
40
Enterprise Database Applications
41
Figure 1-8 An enterprise data warehouse
42
Information Engineering
44
Identify Strategic Planning Factors
45
Identify Corporate Planning Objects
1. Organizational unitsdepartments
2. Organizational locations
3. Business functionsgroups of
business processes
4. Entity typesthe things we are
trying to model for the database
5. Information systemsapplication
programs
46
Develop Enterprise Model
Functional decomposition
Iterative process breaking system description
into finer and finer detail
Enterprise data model
Planning matrixes
Describe interrelationships
between planning objects
47
Figure 2-2 Example of process decomposition of an
order fulfillment function (Pine Valley Furniture)
Decomposition = breaking
large tasks into smaller tasks
in a hierarchical structure
chart
48
Planning
SDLC
System Development Life Cycle
Detailed, well-planned development process
Time-consuming, but comprehensive
Long development cycle
Prototyping
Rapid application development (RAD)
Cursory attempt at conceptual data modeling
Define database during development of initial prototype
Repeat implementation and maintenance activities with
new prototype versions
50
Systems Development Life Cycle
(see also Figures 2.4, 2.5)
Planning
Analysis
Logical Design
Physical Design
Implementation
Maintenance
51
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Planning
Planning Purposepreliminary understanding
Deliverablerequest for study
Analysis
Logical Design
Physical Design
52
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Planning Purposethorough requirements analysis and
structuring
Deliverablefunctional system specifications
Analysis
Analysis
Logical Design
Physical Design
53
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Planning Purposeinformation requirements elicitation
and structure
Deliverabledetailed design specifications
Analysis
Logical Design
Logical Design
Physical Design
Physical Design
Physical Design
Logical Design
Physical Design
Database activity
database implementation, Implementation
Implementation
including coded programs,
documentation, Maintenance
installation and conversion
56
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Planning Purposemonitor, repair, enhance
Deliverableperiodic audits
Analysis
Logical Design
Physical Design
Database activity
database maintenance, Implementation
performance analysis
and tuning, error Maintenance
Maintenance
corrections
57
Prototyping Database Methodology
(Figure 2.6)
58
Prototyping Database Methodology
(Figure 2.6) (cont.)
59
Prototyping Database Methodology
(Figure 2.6) (cont.)
60
Prototyping Database Methodology
(Figure 2.6) (cont.)
61
Prototyping Database Methodology
(Figure 2.6) (cont.)
62
CASE
64
Managing Projects
65
Managing Projects: People Involved
Business analysts
Systems analysts
Database analysts and data modelers
Users
Programmers
Database architects
Data administrators
Project managers
Other technical experts
66
Figure 2-7 Three-schema architecture
Different people
have different
views of the
databasethese
are the external
schema
The internal
schema is the
underlying
design and
implementation
67
Figure 2-8 Developing the three-tiered architecture
68
Figure 2-9 Three-tiered client/server database architecture
69
DATABASE MANAGEMENT SYSTEMS (DBMS I)