0% found this document useful (0 votes)
24 views28 pages

BIS Lecture 01 - Introduction

Uploaded by

aastproject10
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
24 views28 pages

BIS Lecture 01 - Introduction

Uploaded by

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

BIS315E

Advanced Database Systems

© Dr. Mohamed Saleh


Reference Book:
R. Elmasri and S. Navathe, “Database
Systems”, Addison Wesley, 9th edition,
2021.

Evaluation System:
1. 7th Week (2 Assignments) : 30
points
2. 12th Week (2 Sheets + Project) : 20
points
3. Class attendance : 10
points
Course Outline
1. Fundamental database concepts
2. The ER-Model
3. The enhanced ER-Model
4. The relational data model (RDM)
5. SQL (8 Lessons)
BIS315E
Advanced Databases

Lecture 1:
Fundamental Database
Concepts
Overview
 Database environment and
Client/Server architecture
 Database, data, information, and
metadata
 Evolution of database systems
 Advantages of databases
 Costs and risks of databases
 Categories of databases
 Components of database environment
5
Database Environment
 Database Environment : refers to the system, software,
hardware, and networking components that facilitate the
storage, management, retrieval, and manipulation of data in a
database. Key elements of a database environment include:
 Database Management System (DBMS): Software that
enables users to interact with the database. Examples include
MySQL, Oracle, SQL Server, etc.
 Data: Information stored in the database, organized in tables
with rows and columns.
 Hardware: Servers, storage devices, and other physical
components where the database is stored.
 Software: Operating systems, networking software, and
applications that interact with the database.
 Users: Individuals or applications that access and manipulate
the data stored in the database.

6
Client/Server Architecture
 Client/server architecture is a computing model where tasks are
divided between clients and servers in a network. Clients
request services or resources from servers, which fulfill these
requests. Key components of client/server architecture include:
 Client: A user interface that requests services or resources
from the server. Clients can be desktop computers, laptops,
mobile devices, or other systems.
 Server: A centralized system that provides services or
resources to clients. Servers can be dedicated hardware or
software applications running on a computer.
 Network: The communication infrastructure that enables
clients and servers to interact with each other.
 Request-Response Model: Clients send requests to servers,
which process these requests and send back responses with the
requested information or services.
 Scalability: Client/server architectures are scalable, allowing
for easy addition of more clients or servers to meet changing
demands.

7
Figure 1-11
Components
of the
database
environment

Metadata Data 8
9
Definitions
 Database - organized collection of logically
related data
 Data - stored representations of meaningful
objects and events
 Structured: numbers, text, dates

 Unstructured: images, video, documents

 Information: data processed to increase


knowledge of the user
 Data is transformed into information through processing,
organization, and analysis.
 Metadata: data that describes the properties
and context of user data (data about data)

10
Figure 1-1a Converting data to information
- data in context

11
Converting data into information
 Converting data into information is a critical process in
data management and decision-making.
 Data itself is raw and unorganized
 information is processed data that is meaningful and
useful.
Here's a breakdown of how data can be converted into
information:
Data Collection:
•Raw Data: This is unprocessed data collected from various
sources like sensors, surveys, transactions, etc.
•For example, sales records, customer feedback,
temperature readings, etc.
•Example: Imagine you have raw data from a retail store
showing sales transactions:
•Date: 2024-08-25
•ProductID: 101
•Quantity:
Date 5 ProductID Quantity Price Location
•Price: $20
2024-08-25 101 5 $20 Store A
12
2024-08-25 102 3 $15 Store B
Converting data into information

. Data Organization:
• Sorting and Structuring: Arrange data into a logical
format, such as databases, tables, or spreadsheets.
Organizing the data helps in retrieving it efficiently.
• Example: Organizing sales data into a table by
product, date, and location:
Date ProductID Quantity Price Location
2024-08-25 101 5 $20 Store A
2024-08-25 102 3 $15 Store B

Data Cleaning: correcting mistakes, removing duplicates, handling


missing values.
Data Processing: using calculations, aggregations, or algorithms to
derive meaningful patterns.
Data Analysis: find trends, correlations, or anomalies.
Date ProductID Quantity Price Location
Visualization: Use visual tools like charts, graphs, or dashboards
2024-08-25 101 5 $20 Store A
13
2024-08-25 102 3 $15 Store B
Converting data into information

Graphical displays turn data into


useful information that managers
can use for decision making and
interpretation 14
Metadata
 Data that describes the properties and
context of user data (data about data)

15
Metadata
 metadata refers to the information that
describes the structure, organization, and
characteristics of the data stored within the
database.
 Examples of metadata
 Schema Metadata: Table Definitions, Indexes,
Relationships
 Data Dictionary
 Storage Metadata
 Security Metadata
16
Evolution of Database
Systems
 Flat files (not database) - 1960s -
1980s
 Hierarchical – 1970s - 1990s
 Network – 1970s - 1990s
 Relational – 1980s - present
 Object-oriented – 1990s - present
 Object-relational – 1990s - present
 Data warehousing – 1980s - present
 Web-enabled – 1990s - present

17
DATABASE Approach
 Central repository of shared data
 Stored in a standardized,

convenient form
 Requires a Database Management

System (DBMS)
 A software system that is used to create,
maintain, and provide controlled access to user
databases

18
19
Advantages of database approach
 1. Data Integrity and Accuracy:
• Consistency constraints and validation rules prevent incorrect or
duplicate data from being entered.
• Centralized Control: Data is stored in a centralized location,
ensuring that everyone accesses and updates the same data
1. Entity Integrity
• Example: In a customer database, each customer must have a unique
identifier (like a Customer ID). If two customers have the same ID, it violates
entity integrity.
2. Referential Integrity
• Example: In an order management system, every order must reference a valid
customer. If an order references a customer ID that doesn’t exist in the
customer table, it violates referential integrity.
3. Domain Integrity
• Example: A database field for "Age" should only accept numerical values
within a certain range (e.g., 0 to 120). If a user enters "abc" or "150", it
violates domain integrity.
4. Unique Constraints
• Example: An email address in a user table must be unique. If two users
attempt to register with the same email address, it violates the unique
constraint.
20
Advantages of database approach
 2. Reduced Data Redundancy:
• Elimination of Duplication: In traditional file-based systems,
data is often duplicated across multiple files, leading to
inefficiencies. The database approach reduces redundancy by
organizing data into related tables and ensuring that each piece
of data is stored only once.
 3. Enhanced Data Security:
• Access Control: Database Management Systems (DBMS) allow
administrators to define access levels, ensuring that only
authorized users can view or modify specific data.
• Encryption: Data can be encrypted both at rest and in transit,
protecting it from unauthorized access or breaches.

21
Advantages of database approach
 4. Improved Data Sharing and Accessibility:
• Multi-User Access
• Remote Access
 5. Efficient Data Retrieval and Querying:
• Query Capabilities: Databases use powerful query languages
like SQL, which allow users to quickly retrieve and manipulate
data.
• Indexing: Databases often use indexing to speed up data
retrieval, improving performance, especially with large datasets.
 6. Scalability:
Handles Large Volumes of Data
 7. Improved Data Backup and Recovery:
Automated Backups
Disaster Recovery
 8. Improved Decision-Making :
Comprehensive Data Analysis, Data Mining

22
 Costs of the Database Approach:
1. Initial Setup Costs:
1. Hardware and Software: Setting up a database system
requires purchasing hardware, database management
software, and potentially licensing fees.
2. Installation and Configuration: can be complex and may
require specialized expertise.
2. Maintenance Costs:
1. Ongoing Maintenance: Regular maintenance, such as
updates, patches, and backups, requires time and resources.
2. Performance Tuning: Ensuring the database operates
efficiently
3. Training Costs:
1. Staff Training: Personnel need to be trained

2. Data Conversion Costs:

3. Migration: Converting existing data from old systems

4. Security Costs:
1. Implementing Security Measures: To protect data, security
protocols like encryption, access controls, and monitoring
systems
24
 Risks of the Database Approach:
1. Data Security and Privacy:
1. Data Breaches (break): Centralizing data in a database can
make it a target for hackers, leading to potential breaches and
data theft.
2. Misuse of Data: Improper access controls can result in
unauthorized users accessing sensitive information.
2. System Downtime:
1. Availability Issues: If the database system goes down due to
a crash, maintenance, or other issues, it can disrupt business
operations.
2. Disaster Recovery: In case of a disaster, restoring the
database may be challenging and time-consuming
3. Data Integrity Risks:
1. Data Corruption: Improper handling, software bugs, or
hardware failures can lead to data corruption.
2. Human Error: Mistakes during data entry, updates, or
maintenance can compromise data accuracy.
4. Vendor Lock-In:
1. Dependency on Specific Vendors

25
Components of the
Database Environment
 CASE Tools – Computer-Aided Software Engineering
 Repository – centralized storehouse of metadata
 Database Management System (DBMS) – software
for managing the database
 Database – storehouse of the data
 Application Programs – software using the data
 User Interface – text and graphical displays to users
 Data Administrators – personnel responsible for
maintaining the database
 System Developers – personnel responsible for
designing databases and software
 End Users – people who use the applications and
databases
26
Database Constraints
 In a database, constraints are rules applied to
table columns to enforce data integrity,
consistency, and accuracy. Constraints help ensure
that only valid data is entered into the database,
preventing errors and maintaining the quality of
the data.

27
Big Names in Database Systems
The big commercial database

Company Product vendors Remarks


 Oracle Oracle 8i, 9i, etc. World’s 3rd largest software company
 IBM DB2, Universal Server World’s 2nd largest after MS
 Microsoft Access, SQL Server Access comes with MS Office
 Sybase SAP Adaptive Server Number 2 database systems
 Informix Dynamic Server Acquired by IBM in 2001

 Some free (open source) database systems


• PostgreSQL (often referred to as Postgres)
• MySQL
• Predator
Match terms and definitions
1. Data a. Data placed in context or
2. Database summarized
application b. Application program
3. Repository c. Facts, text, graphics, etc.
4. Metadata d. A graphical model about an
5. Information organization
6. DBMS e. Organized collection of related
7. Database data
8. ERP f. Data definitions and constraints
9. Enterprise g. Centralized storehouse for all
data model data definitions
h. An integrated enterprise level MIS

i. A software application to create,


29

You might also like