Lecture 1-1

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 16

Introduction

Course Code: ICT-331


Credit Hours: 4(3-1)
course Tittle: Database Administration and
Management
Theory Class: 1hour
Practical Class: 3 hours
Mid marks: 18
sessional: 12
Practical marks: 20
Final Marks: 30
Total Marks: 80
Course Name: Database administration and
management
Course Code: ICT-605
Credit Hours: 3(2-1)
Topic: (Introduction to database system,
Data models)
Level: BS
Lecture # 1
Department of Information Technology , Government College Women University Faisalabad
Introduction
• A database-management system (DBMS) is a
collection of interrelated data and a set of
programs to access those data. The collection
of data, usually referred to as the database,
contains information relevant to an enterprise.
The primary goal of a DBMS is to provide a
way to store and retrieve database
information that is both convenient and
efficient.
Modes in databases
• Two modes in which databases are used.
1. The first mode is to support online transaction processing,
where a large number of users use the database, with
each user retrieving relatively small amounts of data, and
performing small updates. This is the primary mode of use
for the vast majority of users of database applications
such as those that we outlined earlier.
2. The second mode is to support data analytics, that is, the
processing of data to draw conclusions, and infer rules or
decision procedures, which are then used to drive
business decisions.
View of Data

• A database system is a collection of


interrelated data and a set of programs that
allow users to access and modify these data. A
major purpose of a database system is to
provide users with an abstract view of the
data. That is, the system hides certain details
of how the data are stored and maintained.
Data Models

• Underlying the structure of a database is the data


model: a collection of conceptual tools for describing
data, data relationships, data semantics, and
consistency constraints.
• The data models can be classified into four different
categories:
• Relational Model
• Entity-Relationship Model
• Semi-structured Data Model
• Object-Based Data Model.
Relational Model
• The relational model uses a collection of tables to
represent both data and the relationships among those
data. Each table has multiple columns, and each
column has a unique name. Tables are also known as
relations. The relational model is an example of a
record-based model.
• Record-based models are so named because the
database is structured in fixed-format records of several
types. Each table contains records of a particular type.
Each record type defines a fixed number of fields, or
attributes.
Entity-Relationship Model
• The entity-relationship (E-R) data model uses a
collection of basic objects, called entities, and
relationships among these objects. An entity is
a “thing” or “object” in the real world that is
distinguishable from other objects.
Semi-structured Data Model
• The semi-structured data model permits the
specification of data where individual data
items of the same type may have different
sets of attributes. This is in contrast to the
data models mentioned earlier, where every
data item of a particular type must have the
same set of attributes. JSON and Extensible
Markup Language (XML) are widely used
semi-structured data representations.
Object-Based Data Model
• Object-oriented programming (especially in Java, C++,
or C#) has become the dominant software-development
methodology. This led initially to the development of a
distinct object-oriented data model, but today the
concept of objects is well integrated into relational
databases. Standards exist to store objects in relational
tables. Database systems allow procedures to be stored
in the database system and executed by the database
system. This can be seen as extending the relational
model with notions of encapsulation, methods, and
object identity.
Data Abstraction

• For the system to be usable, it must retrieve data


efficiently. The need for efficiency has led database
system developers to use complex data structures to
represent data in the database. Since many database-
system users are not computer trained, developers hide
the complexity from users through several levels of data
abstraction, to simplify users’ interactions with the
system:
• Physical level
• Logical level
• View level.
Physical level.
• The lowest level of abstraction describes how
the data are actually stored. The physical level
describes complex low-level data structures in
detail.
Logical level
• The next-higher level of abstraction describes what data
are stored in the database, and what relationships exist
among those data. The logical level thus describes the
entire database in terms of a small number of relatively
simple structures. Although implementation of the
simple structures at the logical level may involve
complex physical-level structures, the user of the logical
level does not need to be aware of this complexity. This
is referred to as physical data independence. Database
administrators, who must decide what information to
keep in the database, use the logical level of abstraction.
View Level
• .The highest level of abstraction describes only part
of the entire database. Even though the logical
level uses simpler structures, complexity remains
because of the variety of information stored in a
large database. Many users of the database system
do not need all this information; instead, they
need to access only a part of the database. The
view level of abstraction exists to simplify their
interaction with the system. The system may
provide many views for the same database.
Instances and Schemas

• Databases change over time as information is inserted and


deleted. The collection of information stored in the database
at a particular moment is called an instance of the database.
The overall design of the database is called the database
schema. The concept of database schemas and instances
can be understood by analogy to a program written in a
programming language. A database schema corresponds to
the variable declarations (along with associated type
definitions) in a program. Each variable has a particular
value at a given instant. The values of the variables in a
program at a point in time correspond to an instance of a
database schema.
Physical and Logical schema
• Database systems have several schemas,
partitioned according to the levels of abstraction.
• The physical schema describes the database
design at the physical level, while the logical
schema describes the database design at the
logical level. A database may also have several
schemas at the view level, sometimes called
subschemas, that describe different views of the
database.

You might also like