Providing storage structures (INDEXES) for
efficient query processing
The performance is very slow due
to traffic is very high
The processing depends on one server
so it has SINGLE POINT OF FAILURE
for database and application
Database is a single point of failure
High cost for maintenance due to
redundancy of thick client
Application layer is not a single
point of failure
Database is a single point of failure
Application is a single point of failure
low cost for maintenance due to
redundancy of thick client
IT professional who works on creating, maintaining, querying, and tuning the database of the organization.
They are also responsible for maintaining data security and integrity. This role requires the professionals to
have good knowledge and experience in the particular RDBMS that the company uses. Based on the
requirements of the company
They maintain and run the databases and servers of the
organization. They are mainly concerned with the security patches,
replication, and backup of data.
They work on developing SQL queries and stored procedures to meet the
requirements of the business. They specialize in database development.
They design schemas, build data structures, table indexes, and relationships. They are mainly
responsible for building a structure the meets the business requirements in a specific area.
They merge data from numerous data sources and store them in a data warehouse.
Done using QUERY PROCESSING
AND OPTIMIZATION module
it is the allowing the program-data
independence and program-operation
Efficiency independence
Data abstraction
done thru conceptual
representation of data
ex. data model
Data is stored in a standardized, convenient form
Central repository of shared data
accessibility done thru metadata and
Self-describing nature of database
conceptual model
program data independence is
Insulation between programs data
done as the structure of data file is
and data abstraction
is stored in the metadata
ex done using
1- SPECIFYING DATA TYPE
2- UNIQUENESS of data item values
Enforcing integrity Constrains
Done by:Database designers by
identifying integrity constraints
in database design phase
The effects of an accomplished transaction are permanently recorded in the database and must not get lost or
Durability vanished due to subsequent failure. So this becomes the responsibility of the recovery sub-system to ensure
durability.
A transaction must alter the database from one steady-state to another steady state. This is
the responsibility of both the DBMS and the application developers to make certain
Consistency
consistency. The DBMS can ensure consistency by putting into effect all the constraints that
Advantages procedure of managing simultaneous transactions ‫مع التاكد من‬ have been mainly on the database schema such as integrity and enterprise constraints.
Concurrency Control
their ACID properties
The 'all or nothing' property. A transaction is an indivisible entity that is either performed in its entirety or will not get
Atomicity
performed at all. This is the responsibility or duty of the recovery subsystem of the DBMS to ensure atomicity.
Transactions that are executing independently of one another is the primary concept followed by isolation. In other
Sharing of data and multiuser words, the frictional effects of incomplete transactions should not be visible or come into notice to other transactions
Isolation
going on simultaneously. It is the responsibility of the concurrency control sub-system to ensure adapting the
isolation.
Each user can see a view
Support of multiple VIEWS
‫كل قسم ليه اكسيس على جزء معين من الداتابيز‬
Eliminate wastage of storage
space and and INCONSISTENCY
controlling the redundancy
IS Done using views and all data is
stored in only one place
Done using security and
authorization subsystem
Restricting unauthorized access
done by DBA
ex.: query language for casual users
Providing multiple user interfaces programing for application
menu driven for stand-alone users
providing backup and recovery done using RECOVERY SUBSYSTEM
Stores objects PERMANENTLY
Providing persistent storage for
,such an object is called
sustainability program objects
PERSISTENT ‫متواصل‬
Representing complex
Done using ERD
relationships among data
Permitting inferencing and action
using rules
Needs expertise to use
DBMS is expensive
Disadvantages
Maybe incompatible with any other We can solve this problem by using a third party tool that can
available DBMS facilitate the transfer process
Process quiers that are coming
from UI Application
Ex: table name, column name, data type,
Database systems Main components Metadata (DB definition)>> DB catalogue
constrains, DB objects structure
Access the database
Ex: name, age, salary, address,
Stored DB (DB itself)
phone number
Represent a set of final data which
External schema accessed only by specific type of
users
These shapes are independent
from other entities, and are often
called parent entities, since they
will often have weak entities that
depend on them. They will also
have a primary key, distinguishing
each occurrence of the entity.
Strong entity
Strong Entity Symbol
Weak entities depend on some
other entity type. They don't have
primary keys, and have no
meaning in the diagram without
their parent entity.
ERD entity symbols
Weak entity
Weak Entity Symbol
Associative entity Associative
entities relate the instances of
several entity types. They also
contain attributes specific to the
relationship between those entity
instances.
Associative entity symbol
AssociativeEntity.png
Relationships are associations
between or among entities.
Relationship Symbol
Relationship
Within entity-relationship
diagrams, relationships are used to
document the interaction between symbol
two entities. Relationships are
ERD relationship symbols usually verbs such as assign,
associate, or track and provide
(Database) useful information that could not
Conceptual schema schema that contains all types and ‫زى الريندر بتاع ديزاين المبانى‬ be discerned with just the entity
relation between data types.
Weak relationship
Weak Relationship Symbol
Weak Relationships are
connections between a weak entity
and its owner.
Attributes are characteristics of an
entity, a many-to-many
three schema Architecture relationship, or a one-to-one
relationship.
Attribute
Attribute Symbol
Multivalued attributes are those
that are can take on more than one
value.
Multivalued attribute
Multivalued Attribute Symbol
ERD attribute symbols
Derived attribute
Derived Attribute Symbol
Derived attributes are attributes
whose value can be calculated
DONE thru XML DBSM Connection with web HTML Connection with another language
from related attribute values.
components : dummy terminals and central database and application server
disadvantage processing : depends on one main server Mainframe environment
application layer: depends on one main server
Relationship
Relationship Symbol
Disadvantage Relationships are associations
Setup : dummy terminals and central database and application server between or among entities.
processing : depends on one main server Client/server environment
application layer : SETUP AND INSTALLATION FOR THE APPLICATION called THICK CLIENT
Advantage
Fields
DBMS environment Explain the allocation of the data
on the disk (the data at the end is a
group of files stored on my hard Field.png
Disadvantage DETAILED DESIGN ‫لوحات التصميمم‬
Setup : Central database and central application server Physical schema disk so the physical path of each
‫لالقسام كلها‬
processing : depends on one main server file and what is physical location on
application layer : SETUP AND INSTALLATION FOR THE APPLICATION called THIN CLIENT the hard disk and what is allocated
space)
Advantage
Keys
internet computing environment
used to solve the single point of (Three - tier- architecture) Keys.png
failure in application server used in case of high load on the
N- tier
application server which contains a full design of
used in case of multiple application database schema including entities ‫لوحات تصميم االقسام كلها بس‬
Types :
and relationships SCHEMATIC PHASE
Logical Model (Concepual Model) EX. (ERD)
1st Tier : database server
2nd Tier: application server 3-Tier
3rd Tier : Thin client used to implement the physical
data independence
Data Models
Which explain how my data stored in hard disk and
which access path which facilitated the searching a
Architecture and data models process
Physical Model The physical model represent by ( Physical schema )
Some fragments of the database
may be replicated whereas others Partial used to implement the physical
may not. Replication: COPY AND PAST data independence
One working and one is standby Full the Unified Modeling
Language (UML) diagram.
Fragmentation: CUT AND PAST
Entity Relationship Diagram
(ERD) and
Distributed database : To support
the availability of the database
DBMS
Administrative DBA
Database administrator (DBA) Actors on The scene
Development DBA
Types of DBAs
Data Architect There are a lot of approaches when
it comes to developing data
Data-modeling techniques
DBMS SCENE WORKERS models, but two common methods
Data Warehouse DBA are
design and implement the DBMS
DBMS system designers and
modules and interfaces as a
implementers
software package.
design and implement tools like
Tool developers
add ons in revit or lisbs in cad
Workers behind the scene
(system administration personnel)
are responsible for the actual
running and maintenance of the Operators and maintenance
hardware and software personnel
environment for the database
system.
Create, Drop, Truncate, Rename. Data Definition Language (DDL) image-75.jpg
Select, Insert, Delete, Update. Data Manipulation language (DML)
DBMS Languages
Revoke, Grant. Data Control Language (DCL) png.‫ؤؤؤؤ‬
Transaction Control Language
Rollback, Commit
(TCL)
Data modeling ‫هو المخططات اللى بنعملها ديزاين زى شغل الكاد دة‬
These visual representations are called data models.
You can think of data modeling as a blueprint of a house. At any point, there might be
electricians, carpenters, and plumbers using that blueprint. Each one of these builders
data model ‫ايه هو ال‬
has a different relationship to the blueprint, but they all need it to understand the
overall structure of the house. Data models are similar; different users might have
different data needs, but the data model gives them an understanding of the structure
as a whole.
UML Entity Relationship
download.png
1 : 1 - one to one relationship
1 : 0..1 - one to zero or one relationship
1 : N - one to many relationship
1 : 1..N - one to one and more relationship
1 : 0..N - one to zero and more relationship
N : N - one to many relationship
1..N : 1..N - one or more to one or more relationship
0..N : 0..N - zero or more to zero or more relationship
You can create various combinations of cardinality. The cardi
NOTATIONS
NOTATIONS
Crow Foot
7a3da7a2bd14f08e334ca1bfc5669c44.png
Chen
Mappings Is the process of transferring the requests and result between the levels
A set of final data which accessed
External Schema
by specific type of users
Contains all the tables, all relations
DB Archericture Conceptual Schema
between the data
Explains the allocation of the data
Physical Schema
on the disk
Why he need for system
If he is changing data regularly or
What is his nature of using database
gather the info from the customer he is adding data every day
Users will use the database and
Step 1 : Analysis and requirement how many users we have
System Analyst
gathering.
know the budget
understand the business model
setting expectations with the
customer
taking the requirements from the
analyst
creating model (converting the
Step 2 : DB Design Database Designer
requirements to CONCEPTUAL
SCHEMA)
Cycle of creating DB 2
creating the final model
create DB Schema (tables) that are
designed Conceptually
setup the DBMS
Implementaion (transfer
Step 3 Database Adminstrator populate the initial data
to tables and DB objects)
create users and authorize/restrict
access
maintain DB Performance
develop the application from
scratch
Step 4 Create the UI (End User Application) Application Programmer
test and debug the application
conduct the end user training
Menu driven interface &form style
Graphical user interface (GUI)
interface
Deductive database system
provides active rules that automatically INITIATE ACTIONS
Active database system
when certain EVENTS AND CONDITIONS OCCUR
procedure of managing simultaneous transactions ensuring their
Concurrency Control
atomicity, isolation, consistency, and serializability
is the process of taking all of your data from disparate sources throughout
Consolidation your organization, cleaning it up, and combining it in a single location,
such as a cloud data warehouse or lakehouse environment.
A way to optimize the performance of a database by minimizing
Indexing
the number of disk accesses required when a query is processed.
XML has found wide application. Today, various programs and devices use it to handle, structure, store, transmit,
and display data. For example, it's widely used in B2B data exchanges. XML is also the standard for Office file
formats, including Microsoft Office and Google Docs files.
XML(Extended Markup language )
The key difference between HTML and XML is that HTML displays data and describes the
structure of a webpage, whereas XML stores and transfers data.
Entity relationship diagram (ERD) shows the relationships of entity sets stored in a database. https://www.mindmeister.com/map/2302481583
s a form of client-server architecture. Specifically, it is a networked computer system
THICK CLIENT
with most resources installed locally, rather than distributed over a network.
GLOSSARY A transaction is an action or series of actions that are being performed by a single user or application program, which reads or updates the contents
of the database.
transactions
A transaction can be defined as a logical unit of work on the database. This may be an entire program, a piece of a program, or a single command
(like the SQL commands such as INSERT or UPDATE), and it may engage in any number of operations on the database. In the database context, the
execution of an application program can be thought of as one or more transactions with non-database processing taking place in between.
Transactions that are executing independently of one another is the primary concept followed by isolation. In other
words, the frictional effects of incomplete transactions should not be visible or come into notice to other transactions
Isolation
going on simultaneously. It is the responsibility of the concurrency control sub-system to ensure adapting the
isolation.
The 'all or nothing' property. A transaction is an indivisible entity that is either performed in its entirety or will not get
Atomicity
performed at all. This is the responsibility or duty of the recovery subsystem of the DBMS to ensure atomicity.
A transaction must alter the database from one steady-state to another steady state. This is
the responsibility of both the DBMS and the application developers to make certain
Consistency
consistency. The DBMS can ensure consistency by putting into effect all the constraints that
have been mainly on the database schema such as integrity and enterprise constraints.
The effects of an accomplished transaction are permanently recorded in the database and must not get lost or vanished due
Durability
to subsequent failure. So this becomes the responsibility of the recovery sub-system to ensure durability.
modules for implementing the catalog, query language processing, interface processing, accessing and buffering data,
Modules, controlling concurrency, and handling data recovery and security. The DBMS must interface with other system software
such as the operating system and compilers for various programming languages.
Data Abstraction in dbms refers to
the process of hiding irrelevant
the process of hiding irrelevant
details from the user.
details from the user.
access path describes how records in a database file are retrieved.
DBMS
1. Advantages

Link:
https://www.youtube.com/watch?v=YcYF-kxE0Sw&list=PLBlnK6fEyqRi_CUQ-FXxgzKQ1dwr_ZJWZ&index=4

1.1. Efficiency

1.1.1. Providing storage structures (INDEXES) for efficient query processing

1.1.1.1. Done using QUERY PROCESSING AND OPTIMIZATION module

1.1.2. Data abstraction

1.1.2.1. it is the allowing the program-data independence and program-operation independence

1.1.2.2. done thru conceptual representation of data

1.1.2.3. ex. data model

1.2. accessibility

1.2.1. Data is stored in a standardized, convenient form

1.2.2. Central repository of shared data

1.2.3. Self-describing nature of database

1.2.3.1. done thru metadata and conceptual model

1.2.4. Insulation between programs data and data abstraction

1.2.4.1. program data independence is done as the structure of data file is is stored in the metadata

1.3. Sharing of data and multiuser

1.3.1. Enforcing integrity Constrains

1.3.1.1. ex done using 1- SPECIFYING DATA TYPE 2- UNIQUENESS of data item values

1.3.1.2. Done by:Database designers by identifying integrity constraints in database design phase

1.3.2. Concurrency Control

1.3.2.1. procedure of managing simultaneous transactions ‫ مع التاكد من‬their ACID properties

1.3.2.1.1. Durability

1.3.2.1.1.1. The effects of an accomplished transaction are permanently recorded in the database and must not get lost or vanished due to subsequent failure. So this becomes the responsibility of the recovery sub-system to ensure durability.

1.3.2.1.2. Consistency

1.3.2.1.2.1. A transaction must alter the database from one steady-state to another steady state. This is the responsibility of both the DBMS and the application developers to make certain consistency. The DBMS can ensure consistency by putting into effect all the constraints that have been mainly on the database schema such as integrity and enterprise constraints.

1.3.2.1.3. Atomicity

1.3.2.1.3.1. The 'all or nothing' property. A transaction is an indivisible entity that is either performed in its entirety or will not get performed at all. This is the responsibility or duty of the recovery subsystem of the DBMS to ensure atomicity.

1.3.2.1.4. Isolation

1.3.2.1.4.1. Transactions that are executing independently of one another is the primary concept followed by isolation. In other words, the frictional effects of incomplete transactions should not be visible or come into notice to other transactions going on simultaneously. It is the responsibility of the concurrency control sub-system to ensure adapting the isolation.

1.3.3. Support of multiple VIEWS

1.3.3.1. Each user can see a view ‫كل قسم ليه اكسيس على جزء معين من الداتابيز‬

1.3.4. controlling the redundancy

1.3.4.1. Eliminate wastage of storage space and and INCONSISTENCY

1.3.4.2. IS Done using views and all data is stored in only one place

1.3.5. Restricting unauthorized access

1.3.5.1. Done using security and authorization subsystem

1.3.5.2. done by DBA

1.3.6. Providing multiple user interfaces

1.3.6.1. ex.: query language for casual users programing for application menu driven for stand-alone users

1.4. sustainability

1.4.1. providing backup and recovery

1.4.1.1. done using RECOVERY SUBSYSTEM

1.4.2. Providing persistent storage for program objects

1.4.2.1. Stores objects PERMANENTLY ,such an object is called PERSISTENT ‫متواصل‬

1.4.3. Representing complex relationships among data

1.4.3.1. Done using ERD

1.5. Permitting inferencing and action using rules

Link:
https://www.brainkart.com/article/Advantages-of-Using-the-DBMS-Approach_11394/

2. Disadvantages

Link:
https://maharatech.gov.eg/mod/hvp/view.php?id=7135

2.1. Needs expertise to use

2.2. DBMS is expensive

2.3. Maybe incompatible with any other available DBMS

2.3.1. We can solve this problem by using a third party tool that can facilitate the transfer process

3. Database systems Main components

May 24, 2022 11:08

Mohamed Tarek said

https://www.bmc.com/blogs/dbms-database-management-systems/

3.1. Process quiers that are coming from UI Application

3.2. Access the database

Link:
https://maharatech.gov.eg/mod/hvp/view.php?id=7135

3.2.1. Metadata (DB definition)>> DB catalogue

3.2.1.1. Ex: table name, column name, data type, constrains, DB objects structure

3.2.2. Stored DB (DB itself)

3.2.2.1. Ex: name, age, salary, address, phone number

4. Architecture and data models

4.1. three schema Architecture

4.1.1. External schema

4.1.1.1. Represent a set of final data which accessed only by specific type of users

4.1.2. Conceptual schema

4.1.2.1. (Database) schema that contains all types and relation between data

4.1.2.1.1. ‫زى الريندر بتاع ديزاين المبانى‬

4.1.2.1.1.1. ERD entity symbols

4.1.2.1.1.1.1. Strong entity

4.1.2.1.1.1.1.1. These shapes are independent from other entities, and are often called parent entities, since they will often have weak entities that depend on them. They will also have a primary key, distinguishing each occurrence of the entity.

4.1.2.1.1.1.1.2. Strong Entity Symbol

4.1.2.1.1.1.2. Weak entity

4.1.2.1.1.1.2.1. Weak entities depend on some other entity type. They don't have primary keys, and have no meaning in the diagram without their parent entity.

4.1.2.1.1.1.2.2. Weak Entity Symbol

4.1.2.1.1.1.3. Associative entity symbol

4.1.2.1.1.1.3.1. Associative entity Associative entities relate the instances of several entity types. They also contain attributes specific to the relationship between those entity instances.

4.1.2.1.1.1.3.2. AssociativeEntity.png

4.1.2.1.1.2. ERD relationship symbols

4.1.2.1.1.2.1. Within entity-relationship diagrams, relationships are used to document the interaction between two entities. Relationships are usually verbs such as assign, associate, or track and provide useful information that could not be discerned with just the entity types.

4.1.2.1.1.2.1.1. Relationship Symbol Relationship

4.1.2.1.1.2.1.1.1. Relationships are associations between or among entities.

4.1.2.1.1.2.1.1.2. symbol

4.1.2.1.1.2.1.2. Weak relationship

4.1.2.1.1.2.1.2.1. Weak Relationship Symbol

4.1.2.1.1.2.1.2.2. Weak Relationships are connections between a weak entity and its owner.

4.1.2.1.1.3. ERD attribute symbols

4.1.2.1.1.3.1. Attribute

4.1.2.1.1.3.1.1. Attributes are characteristics of an entity, a many-to-many relationship, or a one-to-one relationship.

4.1.2.1.1.3.1.2. Attribute Symbol

4.1.2.1.1.3.2. Multivalued attribute

4.1.2.1.1.3.2.1. Multivalued attributes are those that are can take on more than one value.

4.1.2.1.1.3.2.2. Multivalued Attribute Symbol

4.1.2.1.1.3.3. Derived attribute

4.1.2.1.1.3.3.1. Derived Attribute Symbol

4.1.2.1.1.3.3.2. Derived attributes are attributes whose value can be calculated from related attribute values.

4.1.2.1.1.3.4. Relationship

4.1.2.1.1.3.4.1. Relationship Symbol

4.1.2.1.1.3.4.2. Relationships are associations between or among entities.

4.1.3. Physical schema

4.1.3.1. Explain the allocation of the data on the disk (the data at the end is a group of files stored on my hard disk so the physical path of each file and what is physical location on the hard disk and what is allocated space)

4.1.3.1.1. ‫ لوحات التصميمم‬DETAILED DESIGN ‫لالقسام كلها‬

4.1.3.1.1.1. Fields

4.1.3.1.1.1.1. Field.png

4.1.3.1.1.2. Keys

4.1.3.1.1.2.1. Keys.png

4.2. Data Models

4.2.1. Logical Model (Concepual Model)

4.2.1.1. which contains a full design of database schema including entities and relationships EX. (ERD)

4.2.1.1.1. ‫ لوحات تصميم االقسام كلها بس‬SCHEMATIC PHASE

4.2.1.2. used to implement the physical data independence

4.2.2. Physical Model

4.2.2.1. Which explain how my data stored in hard disk and which access path which facilitated the searching a process The physical model represent by ( Physical schema )

4.2.2.2. used to implement the physical data independence

4.3. Data-modeling techniques

4.3.1. There are a lot of approaches when it comes to developing data models, but two common methods are

4.3.1.1. the Unified Modeling Language (UML) diagram.

4.3.1.2. Entity Relationship Diagram (ERD) and

4.3.1.3. image-75.jpg

4.3.1.3.1. ‫ؤؤؤؤ‬.png

4.4. NOTATIONS
 Link:
https://www.lucidchart.com/pages/ER-diagram-symbols-and-meaning

4.4.1. UML Entity Relationship

4.4.1.1. download.png

4.4.2. Crow Foot

4.4.2.1. NOTATIONS

Link:
https://www.lucidchart.com/pages/ER-diagram-symbols-and-meaning

4.4.2.1.1. 1 : 1 - one to one relationship 1 : 0..1 - one to zero or one relationship 1 : N - one to many relationship 1 : 1..N - one to one and more relationship 1 : 0..N - one to zero and more relationship N : N - one to many relationship 1..N : 1..N - one or more to one or more relationship 0..N : 0..N - zero or more to zero or more relationship You can create various combinations of cardinality. The cardi

4.4.2.2. 7a3da7a2bd14f08e334ca1bfc5669c44.png

4.4.3. Chen
5. DB Archericture
May 24, 2022 11:09

Mohamed Tarek said

https://online.visual-paradigm.com/knowledge/visual-modeling/conceptual-vs-logical-vs-physical-data-model

5.1. External Schema

5.1.1. A set of final data which accessed by specific type of users

5.2. Conceptual Schema

5.2.1. Contains all the tables, all relations between the data
5.3. Physical Schema

5.3.1. Explains the allocation of the data on the disk

6. Mappings

Link:
https://maharatech.gov.eg/mod/hvp/view.php?id=7138&forceview=1

6.1. Is the process of transferring the requests and result between the levels

7. Cycle of creating DB

Link:
https://maharatech.gov.eg/mod/hvp/view.php?id=7136

May 23, 2022 15:24

Mohamed Tarek said

can you share the video please.

May 23, 2022 17:06

Mohamed Tawfik said

https://maharatech.gov.eg/mod/hvp/view.php?id=7136

7.1. Step 1 : Analysis and requirement gathering.

7.1.1. System Analyst

7.1.1.1. gather the info from the customer

7.1.1.1.1. Why he need for system

7.1.1.1.2. What is his nature of using database

7.1.1.1.2.1. If he is changing data regularly or he is adding data every day

7.1.1.1.3. Users will use the database and how many users we have

7.1.1.2. know the budget

7.1.1.3. understand the business model

7.1.1.4. setting expectations with the customer

7.2. Step 2 : DB Design

7.2.1. Database Designer

7.2.1.1. taking the requirements from the analyst

7.2.1.2. creating model (converting the requirements to CONCEPTUAL SCHEMA)

7.2.1.3. creating the final model

7.3. Step 3

7.3.1. Implementaion (transfer to tables and DB objects)

7.3.1.1. Database Adminstrator

7.3.1.1.1. create DB Schema (tables) that are designed Conceptually

7.3.1.1.2. setup the DBMS

7.3.1.1.3. populate the initial data

7.3.1.1.4. create users and authorize/restrict access

7.3.1.1.5. maintain DB Performance

Link:
https://www.dnsstuff.com/how-to-increase-database-performance

7.4. Step 4

7.4.1. Create the UI (End User Application)

7.4.1.1. Application Programmer

7.4.1.1.1. develop the application from scratch

7.4.1.1.2. test and debug the application

7.4.1.1.3. conduct the end user training

8. GLOSSARY
8.1. Graphical user interface (GUI)

8.1.1. Menu driven interface &form style interface

8.2. Deductive database system

8.3. Active database system

8.3.1. provides active rules that automatically INITIATE ACTIONS when certain EVENTS AND CONDITIONS OCCUR

8.4. Concurrency Control

8.4.1. procedure of managing simultaneous transactions ensuring their atomicity, isolation, consistency, and serializability

8.5. Consolidation

8.5.1. is the process of taking all of your data from disparate sources throughout your organization, cleaning it up, and combining it in a single location, such as a cloud data warehouse or lakehouse environment.

8.6. Indexing

8.6.1. A way to optimize the performance of a database by minimizing the number of disk accesses required when a query is processed.

8.7. XML(Extended Markup language )

8.7.1. XML has found wide application. Today, various programs and devices use it to handle, structure, store, transmit, and display data. For example, it's widely used in B2B data exchanges. XML is also the standard for Office file formats, including Microsoft Office and Google Docs files.

8.7.2. The key difference between HTML and XML is that HTML displays data and describes the structure of a webpage, whereas XML stores and transfers data.

8.8. Entity relationship diagram (ERD)

8.8.1. shows the relationships of entity sets stored in a database.

8.8.1.1. https://www.mindmeister.com/map/2302481583

8.9. THICK CLIENT

8.9.1. s a form of client-server architecture. Specifically, it is a networked computer system with most resources installed locally, rather than distributed over a network.

8.10. transactions

8.10.1. A transaction is an action or series of actions that are being performed by a single user or application program, which reads or updates the contents of the database. A transaction can be defined as a logical unit of work on the database. This may be an entire program, a piece of a program, or a single command (like the SQL commands such as INSERT or UPDATE), and it may engage in any number of operations on the database. In the database context, the
execution of an application program can be thought of as one or more transactions with non-database processing taking place in between.

8.11. Isolation

8.11.1. Transactions that are executing independently of one another is the primary concept followed by isolation. In other words, the frictional effects of incomplete transactions should not be visible or come into notice to other transactions going on simultaneously. It is the responsibility of the concurrency control sub-system to ensure adapting the isolation.

8.12. Atomicity

8.12.1. The 'all or nothing' property. A transaction is an indivisible entity that is either performed in its entirety or will not get performed at all. This is the responsibility or duty of the recovery subsystem of the DBMS to ensure atomicity.

8.13. Consistency

8.13.1. A transaction must alter the database from one steady-state to another steady state. This is the responsibility of both the DBMS and the application developers to make certain consistency. The DBMS can ensure consistency by putting into effect all the constraints that have been mainly on the database schema such as integrity and enterprise constraints.

8.14. Durability

8.14.1. The effects of an accomplished transaction are permanently recorded in the database and must not get lost or vanished due to subsequent failure. So this becomes the responsibility of the recovery sub-system to ensure durability.

8.15. Modules,

8.15.1. modules for implementing the catalog, query language processing, interface processing, accessing and buffering data, controlling concurrency, and handling data recovery and security. The DBMS must interface with other system software such as the operating system and compilers for various programming languages.

8.16. Data Abstraction in dbms refers to the process of hiding irrelevant details from the user.

8.16.1. the process of hiding irrelevant details from the user.

8.17. access path

8.17.1. describes how records in a database file are retrieved.

9. ‫ ايه هو ال‬data model

9.1. Data modeling ‫ هو المخططات اللى بنعملها ديزاين زى شغل الكاد دة‬These visual representations are called data models. You can think of data modeling as a blueprint of a house. At any point, there might be electricians, carpenters, and plumbers using that blueprint. Each one of these builders has a different relationship to the blueprint, but they all need it to understand the overall structure of the house. Data models are similar; different users might have different data
needs, but the data model gives them an understanding of the structure as a whole.

10. DBMS Languages

10.1. Data Definition Language (DDL)

10.1.1. Create, Drop, Truncate, Rename.

10.2. Data Manipulation language (DML)

10.2.1. Select, Insert, Delete, Update.

10.3. Data Control Language (DCL)

10.3.1. Revoke, Grant.

10.4. Transaction Control Language (TCL)

10.4.1. Rollback, Commit

11. DBMS SCENE WORKERS

11.1. Actors on The scene

11.1.1. Database administrator (DBA)

Link:
https://intellipaat.com/community/42929/what-is-database-administrator-in-dbms

11.1.1.1. IT professional who works on creating, maintaining, querying, and tuning the database of the organization. They are also responsible for maintaining data security and integrity. This role requires the professionals to have good knowledge and experience in the particular RDBMS that the company uses. Based on the requirements of the company

11.1.1.2. Types of DBAs

11.1.1.2.1. Administrative DBA

11.1.1.2.1.1. They maintain and run the databases and servers of the organization. They are mainly concerned with the security patches, replication, and backup of data.

11.1.1.2.2. Development DBA

11.1.1.2.2.1. They work on developing SQL queries and stored procedures to meet the requirements of the business. They specialize in database development.

11.1.1.2.3. Data Architect

11.1.1.2.3.1. They design schemas, build data structures, table indexes, and relationships. They are mainly responsible for building a structure the meets the business requirements in a specific area.

11.1.1.2.4. Data Warehouse DBA

11.1.1.2.4.1. They merge data from numerous data sources and store them in a data warehouse.

11.2. Workers behind the scene

May 29, 2022 11:13

Mohamed Tarek said

https://www.youtube.com/watch?v=yLc0Yp5QZlU&list=PL37D52B7714788190

11.2.1. DBMS system designers and implementers

11.2.1.1. design and implement the DBMS modules and interfaces as a software package.

11.2.2. Tool developers

11.2.2.1. design and implement tools like add ons in revit or lisbs in cad

11.2.3. Operators and maintenance personnel

11.2.3.1. (system administration personnel) are responsible for the actual running and maintenance of the hardware and software environment for the database system.

12. Distributed database : To support the availability of the database

 12.1. Replication: COPY AND PAST

12.1.1. Partial

12.1.1.1. Some fragments of the database may be replicated whereas others may not.

12.1.2. Full

12.1.2.1. One working and one is standby

12.2. Fragmentation: CUT AND PAST

13. DBMS environment

13.1. Mainframe environment

13.1.1. components : dummy terminals and central database and application server processing : depends on one main server application layer: depends on one main server

13.1.1.1. disadvantage

13.1.1.1.1. The performance is very slow due to traffic is very high

13.1.1.1.2. The processing depends on one server so it has SINGLE POINT OF FAILURE for database and application

13.2. Client/server environment

13.2.1. Setup : dummy terminals and central database and application server processing : depends on one main server application layer : SETUP AND INSTALLATION FOR THE APPLICATION called THICK CLIENT

13.2.1.1. Disadvantage

13.2.1.1.1. Database is a single point of failure

13.2.1.1.2. High cost for maintenance due to redundancy of thick client

13.2.1.2. Advantage

13.2.1.2.1. Application layer is not a single point of failure

13.3. internet computing environment (Three - tier- architecture)

13.3.1. Setup : Central database and central application server processing : depends on one main server application layer : SETUP AND INSTALLATION FOR THE APPLICATION called THIN CLIENT

13.3.1.1. Disadvantage

13.3.1.1.1. Database is a single point of failure

13.3.1.1.2. Application is a single point of failure

13.3.1.2. Advantage

13.3.1.2.1. low cost for maintenance due to redundancy of thick client

13.3.2. Types :

13.3.2.1. N- tier

13.3.2.1.1. used in case of high load on the application server

13.3.2.1.1.1. used to solve the single point of failure in application server

13.3.2.1.1.2. used in case of multiple application

13.3.2.2. 3-Tier

13.3.2.2.1. 1st Tier : database server 2nd Tier: application server 3rd Tier : Thin client

14. Connection with another language

14.1. DBSM Connection with web HTML

14.1.1. DONE thru XML