Unit-1: Introduction To Database: Project Presentation

Project Presentation
UNIT- 1: INTRODUCTION TO
DATABASE
INTRODUCTION TO DATA
DISADVANTAGES OF FILE APPROACH

WHY DATABASE?
DATABASE MANAGEMENT
SYSTEMS
A database management system (DBMS) is a computerized system that enables users

to create and maintain a database.
The DBMS is a general-purpose software system that facilitates the processes of
defining, constructing, manipulating, and sharing databases among various users and
applications.
DATABASE MANAGEMENT SYSTEMS

(CONT.)
Defining a database - involves specifying the data types, structures, and constraints of the data
to be stored in the database. The database definition or descriptive information is also stored
by the DBMS in the form of a database catalog or dictionary; it is called meta-data.
Constructing -the database is the process of storing the data on some storage medium that is
controlled by the DBMS.
Manipulating a database includes functions such as querying the database to retrieve specific
data, updating the database to reflect changes in the miniworld, and generating reports from
the data.
Sharing a database allows multiple users and programs to access the database simultaneously.
DATABASE MANAGEMENT SYSTEMS

(CONT.)
An application program accesses the database by sending queries or requests for data
to the DBMS.
A query typically causes some data to be retrieved; a transaction may cause some data
to be read and some data to be written into the database.
Other important functions provided by the DBMS include protecting the database and
maintaining it over a long period of time. Protection includes system protection against
hardware or software malfunction (or crashes) and security protection against
unauthorized or malicious access.
A typical large database may have a life cycle of many years, so the DBMS must be able
to maintain the database system by allowing the system to evolve as requirements
change over time.
DATABASE SYSTEMS
•DBMS contains information about a particular enterprise
i.Collection of interrelated data
ii.Set of programs to access the data
iii.An environment that is both convenient and efficient to use
•Database systems are used to manage collections of data that are:
i.Highly valuable
ii.Relatively large
iii.Accessed by multiple users and applications, often at the same time.
• A modern database system is a complex software system whose task
is to manage a large, complex collection of data.
•Databases touch all aspects of our lives.
•Database can be of any size and complexity.
PROPERTIES OF DATABASE
A database has the following implicit properties:

■ A database represents some aspect of the real world, sometimes called the
miniworld or the universe of discourse (UoD). Changes to the miniworld are reflected
in the database.
■ A database is a logically coherent collection of data with some inherent meaning. A
random assortment of data cannot correctly be referred to as a database.
■ A database is designed, built, and populated with data for a specific purpose. It has an
intended group of users and some preconceived applications in which these users are
interested.
FUNCTION OF DATABASE
ACTORS
Database administrators –
ON THE SCENE
Naive or parametric end users make up a sizable portion of database end users. Their
The DBA is responsible for authorizing access to the database, coordinating and monitoring its use, and acquiring
main
softwarejobandfunction
hardware revolves
resources asaround constantly
needed. The querying
DBA is accountable forand updating
problems such as the database,
security using
breaches and poor
standard types
system response time.ofIn queries and updates—
large organizations, calledby canned
the DBA is assisted a staff that transactions—that
carries out these functions.have been
Databaseprogrammed
carefully Designers – and tested.
Database designers are responsible for identifying the data to be stored in the database and for choosing appropriate
 Bank customers and tellers check account balances and post withdrawals and deposits.
structures to represent and store this data.
It Reservation agents
is the responsibility or customers
of database for airlines,
designers to communicate hotels,
with and car
all prospective rental
database companies
users check
in order to understand
availability for aand
their requirements given request
to create and
a design thatmake
meets reservations.
these requirements.
End User –
End users are the people whose jobs require access to the database for querying,updating, and generating reports; the
Sophisticated end users include engineers, scientists, business analysts, and others who
database primarily exists for ttheir use. There are several categories of end users:
thoroughly
Casual end-user familiarize
:- occasionalythemselves
access the db with the
but need facilities
different of ime.
info each the DBMS in order to implement
their
Naïveown applications
end –user :- to meet their complex requirements.
Sophisticated end-user –.
Standalone end user :- maintain personal databases by using ready-made program packages that provide easy-to-use
menu-based or graphics-based interfaces. An example is the user of a financial software package that stores a variety of
personal financial data.
System Analysts and application programmers:-
WORKERS BEHIND THE SCENE

In addition to those who design, use, and administer a database, others are associated with the design, development,
and operation of the DBMS software and system environment. These persons are typically not interested in the
database content itself. We call them the workers behind the scene, and they include the following categories:
DBMS system designers and implementers design and implement the DBMS modules and interfaces as a software
package. A DBMS is a very complex software system that consists of many components, or modules, including 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.
Tool developers design and implement tools— the software packages that facilitate database modeling and design,
database system design, and improved performance. Tools are optional packages that are often purchased separately.
They include packages for database design, performance monitoring, natural language or graphical interfaces,
prototyping, simulation, and test data generation. In many cases, independent software vendors develop and market
these tools
Operators and maintenance personnel (system administration personnel) are responsible for the actual running and
maintenance of the hardware and software environment for the database system. Although these categories of workers
behind the scene are instrumental in making the database system available to end users, they typically do not use the
database contents for their own purposes.
ADVANTAGES OF USING THE DBMS

APPROACH
DISADVANTAGES OF DBMS
DATABASE APPLICATIONS EXAMPLES

•Enterprise Information
i.Sales: customers, products, purchases
ii.Accounting: payments, receipts, assets
iii.Human Resources: Information about employees, salaries, payroll taxes.
•Manufacturing: management of production, inventory, orders, supply
chain.
•Banking and finance
i.customer information, accounts, loans, and banking transactions.
ii.Credit card transactions
iii.Finance: sales and purchases of financial instruments (e.g., stocks and
bonds; storing real-time market data
•Universities: registration, grades
DATABASE APPLICATIONS EXAMPLES (CONT..)
•Airlines: reservations, schedules

Telecommunication: records of calls, texts, and data usage, generating monthly
bills, maintaining balances on prepaid calling cards Web-based services
•Online retailers: order tracking, customized recommendations
•Online advertisements
•Document databases
•Navigation systems: For maintaining the locations of varies places of interest
along with the exact routes of roads, train systems, buses, etc.
PURPOSE OF DATABASE SYSTEMS

•In the early days, database applications were built directly on top
of file systems, which leads to:
•Data redundancy and inconsistency: data is stored in multiple file formats resulting in duplication of
information in different files
•Difficulty in accessing data
Need to write a new program to carry out each new task
•Data isolation
Multiple files and formats
Integrity problems
Integrity constraints (e.g., account balance > 0) become “buried” in program code rather than being
stated explicitly
Hard to add new constraints or change existing ones
PURPOSE OF DATABASE SYSTEMS (CONT.)

Atomicity of updates
Failures may leave database in an inconsistent state with partial updates carried out
Example: Transfer of funds from one account to another should either complete or not happen at all
Concurrent access by multiple users
Concurrent access needed for performance
Uncontrolled concurrent accesses can lead to inconsistencies
Ex: Two people reading a balance (say 100) and updating it by withdrawing money (say 50 each) at the
same time
Security problems
Hard to provide user access to some, but not all, data
Database systems offer solutions to all the above

problems
UNIVERSITY DATABASE EXAMPLE

In this text we will be using a university database to illustrate all the
concepts
Data consists of information about:
i.Students
ii.Instructors
iii.Classes
Application program examples:
i.Add new students, instructors, and courses
ii.Register students for courses, and generate class rosters
iii.Assign grades to students, compute grade point averages (GPA) and
generate transcripts
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.
Data models
A collection of conceptual tools for describing data, data relationships, data semantics, and consistency constraints.
Data abstraction
Hide the complexity of data structures to represent data in the database from users through several levels of data abstraction.
STAGES OF DATABASE
Q/A
Define the following terms: data, database, DBMS, database system, database
Catalog,DBA, end user, canned transaction, meta-data, and
transaction-processing application.
1. What four main types of actions involve databases? Briefly discuss each.
2. Discuss the main characteristics of the database approach and how it differs from
traditional file systems.
3. What are the responsibilities of the DBA and the database designers?
4. What are the different types of database end users? Discuss the main activities of
each.
5. Discuss the capabilities that should be provided by a DBMS.
6. Discuss the differences between database systems and information retrieval
systems.
UNIT – 2 Database System

Concepts
and Architecture
Data Models
•Data Model:
A set of concepts to describe the structure of a database, the operations
for manipulating these structures, and certain constraints that the
database should obey.
•Data Model Structure and Constraints:
oConstructs are used to define the database structure
oConstructs typically include elements (and their data types) as well as groups of
elements (e.g. entity, record, table), and relationships among such groups
oConstraints specify some restrictions on valid data; these constraints must be
enforced at all times
Data Models (continued)

Data Model Operations:
These operations are used for specifying database retrievals and updates by
referring to the constructs of the data model.
Operations on the data model may include basic model operations (e.g. generic
insert, delete, update) and user-defined operations (e.g. compute_student_gpa,
update_inventory)
Categories of Data Models

Conceptual (high-level, semantic) data models:
Provide concepts that are close to the way many users perceive data.
(Also called entity-based or object-based data models.)
Physical (low-level, internal) data models:
Provide concepts that describe details of how data is stored in the
computer. These are usually specified in an ad-hoc manner through DBMS
design and administration manuals
Implementation (representational) data models:
Provide concepts that fall between the above two, used by many
commercial DBMS implementations (e.g. relational data models used in
many commercial systems).
Project Presentation DATA MODELS
A collection of tools for describing
Data
Data relationships
Data semantics
Data constraints
Types of data-models:-
Relational model
Entity-Relationship data model (mainly for database design)
Object-based data models (Object-oriented and Object-relational)
Semi-structured data model (XML)
Other older models:
Network model
Hierarchical model
RELATIONAL MODEL
All the data is stored in various tables.
Example of tabular data in the relational model
•Here ID,name,dept_name and salary

are columns.
• the data filled in columns is rows.
A SAMPLE RELATIONAL
DATABASE
Project Presentation ENTITY – RELATIONSHIP
MODEL
Project Presentation COMPONENTS OF E-R
DIAGRAM
Project Presentation HIERARCHIAL MODEL
Project Presentation HIERARCHIAL MODEL
Project Presentation NETWORK MODEL
Project Presentation OBJECT-ORIENTED
MODEL
Schemas versus Instances
Database schema:
The overall design of database.
Skeleton structure of database, it represents logical view of entire
database.
The description of a database.
Includes schema objects like: table,primary key ,views, database
structure, data types, and the constraints on the database.
Schema diagram:
An illustrative display of (most aspects of) a database schema.
Schema construct:
A component of the schema or an object within the schema, e.G.,
Student, course.
Schemas versus Instances
Database State:
The actual data stored in a database at a particular moment in
time. This includes the collection of all the data in the database.
Also called database instance (or occurrence or snapshot).
The term instance is also applied to individual database
components, e.g. record instance, table instance, entity instance
TheProject
actual data
Presentation
in a
DATABASEdatabase may
SCHEMA change quite
VS. frequently.
The data in the database at a particular moment in time is
DATABASE STATE
called a database state or snapshot. It is also called the
current
Databaseset State:of occurrences or instances in the database. In a
given
Refersdatabase
to the content state, each atschema
of a database a momentconstruct
in time. has its own
Initial Database
current set of State:
instances; for example, the STUDENT construct
Refers to the database state when it is initially loaded into the system.
will contain
Valid State:
the set of individual student entities (records) as
itsA instances. Many
state that satisfies database
the structure and states can
constraints bedatabase.
of the constructed to
correspond to a particular database schema. Every time we
insert or delete a record or change the value of a data item in
a record, we change one state of the database into another
state.
Although,
asDATABASE
mentioned earlier,VS.
SCHEMA theDATABASE
schema is not
supposed to changeSTATE frequently, it is not uncommon
(CONTINUED)
that changes occasionally need to be applied to the
Distinction
schema
The database asschema
the application requirements change. For
changes very infrequently.
example,
The database state we changes
may every
decide that
time the another
database data item
is updated.
needs to be stored
Schema is also called intension. for each record in a file, such as
adding
State is alsothe calledDate_of_birth
extension. to the STUDENT schema in
Figure 2.1. This is known as schema evolution. Most
modern DBMSs include some operations for schema
evolution that can be applied while the database is
operational.
EXAMPLE
displays OF
A schema diagram onlyAsome
DATABASEaspects of a schema,
such as the names of record types and data items, and some
SCHEMA
types of constraints. Other aspects are not specified in the
schema diagram; for example, Figure 2.1 shows neither the
data type of each data item nor the relationships among the
various files. Many types of constraints are not represented
in schema diagrams. A constraint such asthestudents
actual instances ofmajoring
The diagram displays the structure of each record
type but not records.
in computer science must take CS1310 before the end of their
sophomore year is quite difficult to represent
diagrammatically.
EXAMPLE OF A DATABASE
STATE
THREE-SCHEMA
ARCHITECTURE
Proposed to support DBMS characteristics of:
Program-data independence.
Support of multiple views of the data.
Not explicitly used in commercial DBMS products, but
has been useful in explaining database system
organization
Project Presentation THREE-SCHEMA
ARCHITECTURE
Defines DBMS schemas at three levels:
Internal schema at the internal level to describe physical storage
structures and access paths (e.g indexes).
• Typically uses a physical data model.
Conceptual schema at the conceptual level to describe the structure
and constraints for the whole database for a community of users.
•Uses a conceptual or an implementation data model.
External schemas at the external level to describe the various user
views.
Usually uses the same data model as the conceptual schema.
THE THREE-SCHEMA
ARCHITECTURE
The three-schema architecture is a convenient tool with which the
user can visualize the schema levels in a database system. Most
DBMSs do not separate the three levels completely and explicitly, but
they support the three-schema architecture to some extent. Some
older DBMSs may include physical-level details in the conceptual
schema. The three-level ANSI architecture has an important place in
database technology development because it clearly separates the
users’ external level, the database’s conceptual level, and the internal
storage level for designing a database. It is very much applicable in the
design of DBMSs, even today. In most DBMSs that support user views,
external schemas are specified in the same data model that describes
the conceptual-level information (for example, a relational DBMS like
Oracle or SQLServer uses SQL for this)
Project Presentation THREE-SCHEMA
ARCHITECTURE
Mappings among schema levels are needed to transform requests and
data.
Programs refer to an external schema, and are mapped by the DBMS to
the internal schema for execution.
Data extracted from the internal DBMS level is reformatted to match the
user’s external view (e.g. formatting the results of an SQL query for display
in a Web page)
DATA INDEPENDENCE
Logical Data Independence:
The capacity to change the conceptual schema without having to change
the external schemas and their associated application programs.
Physical Data Independence:
The capacity to change the internal schema without having to change the
conceptual schema.
For example, the internal schema may be changed when certain file
structures are reorganized or new indexes are created to improve database
performance
Generally, physical
data independence exists in most
databases and file environments where physical details,
such as the exact location of data on disk, and hardware
details of storage encoding, placement, compression,
splitting, merging of records, and so on are hidden from
the user. Applications remain unaware of these details.
On the other hand, logical data independence is harder

to achieve because it allows structural and constraint
changes without affecting application programs—a
much stricter requirement.
Project Presentation Data Independence
(continued)
When a schema at a lower level is changed, only the
mappings between this schema and higher-level schemas
need to be changed in a DBMS that fully supports data
independence.
The higher-level schemas themselves are unchanged.
Hence, the application programs need not be changed
since they refer to the external schemas.
Project Presentation DBMS Languages
Data Definition Language (DDL)
Data Manipulation Language (DML)
High-Level or Non-procedural Languages: These include the relational
language SQL
May be used in a standalone way or may be embedded in a programming
language
Low Level or Procedural Languages:
These must be embedded in a programming language
DBMS Languages
Data Definition Language (DDL):
Used by the DBA and database designers to specify the
conceptual schema of a database.
In many DBMSs, the DDL is also used to define internal and
external schemas (views).
In some DBMSs, separate storage definition language (SDL)
and view definition language (VDL) are used to define internal
and external schemas.
SDL is typically realized via DBMS commands provided to the
DBA and database designers
DBMS Languages
Data Manipulation Language (DML):
Used to specify database retrievals and updates
DML commands (data sublanguage) can be embedded in a general-
purpose programming language (host language), such as COBOL, C, C++, or
Java.
A library of functions can also be provided to access the DBMS from a
programming language
Alternatively, stand-alone DML commands can be applied directly
(called a query language).
Types of DML
High Level or Non-procedural Language:
For example, the SQL relational language
Are “set”-oriented and specify what data to retrieve rather than how to
retrieve it.
Also called declarative languages.
Low Level or Procedural Language:
Retrieve data one record-at-a-time;
Constructs such as looping are needed to retrieve multiple records,
along with positioning pointers.
Project Presentation USER-FRIENDLY DBMS
INTERFACES
Menu-based, popular for browsing on the web
Forms-based, designed for naïve users
Graphics-based
(Point and Click, Drag and Drop, etc.)
Natural language: requests in written English
Combinations of the above:
For example, both menus and forms used extensively in Web database
interfaces
OTHER DBMS INTERFACES
Speech as Input and Output
Web Browser as an interface
Parametric interfaces, e.g., bank tellers using function keys.
Interfaces for the DBA:
oCreating user accounts, granting authorizations
oSetting system parameters
oChanging schemas or access paths
Project Presentation DATABASE SYSTEM
UTILITIES
To perform certain functions such as:
Loading data stored in files into a database. Includes data
conversion tools.
Backing up the database periodically on tape.
Reorganizing database file structures.
Report generation utilities.
Performance monitoring utilities.
Other functions, such as sorting, user monitoring, data
compression, etc.
OTHER TOOLS
Data dictionary / repository:
Used to store schema descriptions and other information such as
design decisions, application program descriptions, user
information, usage standards, etc.
Active data dictionary is accessed by DBMS software and
users/DBA.
Passive data dictionary is accessed by users/DBA only.
OTHER TOOLS
Application Development Environments and CASE (computer-aided
software engineering) tools:
•Examples:
PowerBuilder (Sybase)
JBuilder (Borland)
JDeveloper 10G (Oracle)
Project Presentation TYPICAL DBMS COMPONENT
MODULES
Centralized and
Client-Server DBMS
Architectures
Centralized DBMS:
Combines everything into single system including- DBMS
software, hardware, application programs, and user interface
processing software.
User can still connect through a remote terminal – however, all
processing is done at centralized site.
A Physical Centralized
Architecture
BASIC 2-TIER CLIENT-SERVER
ARCHITECTURES
Specialized Servers with Specialized
functions
Print server
File server
DBMS server
Web server
Email server
Clients can access the specialized servers as
needed
Project Presentation LOGICAL TWO-TIER CLIENT SERVER
ARCHITECTURE
CLIENTS
Provide appropriate interfaces through a client
software module to access and utilize the various
server resources.
Clients may be diskless machines or PCs or
Workstations with disks with only the client
software installed.
Connected to the servers via some form of a
network.
(LAN: local area network, wireless network, etc.)
DBMS SERVER
Provides database query and transaction services to
the clients
Relational DBMS servers are often called SQL
servers, query servers, or transaction servers
Applications running on clients utilize an
Application Program Interface (API) to access server
databases via standard interface such as:
ODBC: Open Database Connectivity standard
JDBC: for Java programming access
Client and server must install appropriate client
module and server module software for ODBC or
JDBC.
TWO TIER CLIENT-SERVER
ARCHITECTURE
A client program may connect to several DBMSs,
sometimes called the data sources.
In general, data sources can be files or other non-
DBMS software that manages data.
Other variations of clients are possible: e.g., in some
object DBMSs, more functionality is transferred to
clients including data dictionary functions,
optimization and recovery across multiple servers,
etc.
THREE TIER CLIENT-SERVER ARCHITECTURE
Common for Web applications
Intermediate Layer called Application Server or Web Server:
Stores the web connectivity software and the business
logic part of the application used to access the
corresponding data from the database server
Acts like a conduit for sending partially processed data
between the database server and the client.
Three-tier Architecture Can Enhance Security:
Database server only accessible via middle tier
Clients cannot directly access database server
Click icon to add picture
THREE-TIER CLIENT-SERVER
ARCHITECTURE
CLASSIFICATION OF DBMS’S
Based on the data model used
Traditional: Relational, Network, Hierarchical.
Emerging: Object-oriented, Object-relational.
Other classifications
Single-user (typically used with personal computers)
vs. multi-user (most DBMSs).
Centralized (uses a single computer with one database)
vs. distributed (uses multiple computers, multiple
databases)
VARIATIONS OF DISTRIBUTED DBMSS (DDBMSS)
Homogeneous DDBMS
Heterogeneous DDBMS
Federated or Multidatabase Systems
Distributed Database Systems have now
come to be known as client-server
based database systems because:
They do not support a totally distributed
environment, but rather a set of database
servers supporting a set of clients.
HISTORY OF DATA MODELS
Network Model
Hierarchical Model
Relational Model
Object-oriented Data Models
Object-Relational Models
Network Model:
The first network DBMS was implemented by Honeywell in
1964-65 (IDS System).
Adopted heavily due to the support by CODASYL
(Conference on Data Systems Languages) (CODASYL - DBTG
report of 1971).
Later implemented in a large variety of systems - IDMS
(Cullinet - now Computer Associates), DMS 1100 (Unisys),
IMAGE (H.P. (Hewlett-Packard)), VAX -DBMS (Digital
Equipment Corp., next COMPAQ, now H.P.).
EXAMPLE OF NETWORK
MODEL SCHEMA
NETWORK MODEL
Advantages:
 Network Model is able to model complex
relationships and represents semantics of
add/delete on the relationships.
 Can handle most situations for modeling using
record types and relationship types.
 Language is navigational; uses constructs like FIND,
FIND member, FIND owner, FIND NEXT within set,
GET, etc.
 Programmers can do optimal navigation through
the database.
NETWORK MODEL
Disadvantages:
 Navigational and procedural nature of processing
 Database contains a complex array of pointers that
thread through a set of records.
 Little scope for automated “query optimization”
Hierarchical Data Model:

 Initially implemented in a joint effort by IBM and North American
Rockwell around 1965. Resulted in the IMS family of systems.
 IBM’s IMS product had (and still has) a very large customer base
worldwide
 Hierarchical model was formalized based on the IMS system
 Other systems based on this model: System 2k (SAS inc.)
HIERARCHICAL MODEL
Advantages:
 Simple to construct and operate
 Corresponds to a number of natural hierarchically organized domains, e.g.,
organization (“org”) chart
 Language is simple:
Uses constructs like GET, GET UNIQUE, GET NEXT, GET NEXT
WITHIN PARENT, etc.
Disadvantages:
 Navigational and procedural nature of processing
 Database is visualized as a linear arrangement of records
 Little scope for "query optimization"
Relational Model:
 Proposed in 1970 by E.F. Codd (IBM), first commercial
system in 1981-82.
 Now in several commercial products (e.g. DB2, ORACLE,
MS SQL Server, SYBASE, INFORMIX).
 Several free open source implementations, e.g. MySQL,
PostgreSQL
 Currently most dominant for developing database
applications.
 SQL relational standards: SQL-89 (SQL1), SQL-92 (SQL2),
SQL-99, SQL3, …
Object-oriented Data Models:
 Several models have been proposed for implementing in a
database system.
 One set comprises models of persistent O-O Programming
Languages such as C++ (e.g., in OBJECTSTORE or VERSANT),
and Smalltalk (e.g., in GEMSTONE).
 Additionally, systems like O2, ORION (at MCC - then
ITASCA), IRIS (at H.P.- used in Open OODB).
 Object Database Standard: ODMG-93, ODMG-version 2.0,
ODMG-version 3.0.
Object-Relational Models:
 Most Recent Trend. Started with Informix
Universal Server.
 Relational systems incorporate concepts from
object databases leading to object-relational.
 Exemplified in the latest versions of Oracle-10i,
DB2, and SQL Server and other DBMSs.
 Standards included in SQL-99 and expected to be
enhanced in future SQL standards.
Project Presentation Q/A (cont..)
1) What is the difference between a database schema and a database state?
2) Describe the three-schema architecture. Why do we need mappings among
schema levels? How do different schema definition languages support this
architecture?
3) What is the difference between logical data independence and physical data
independence? Which one is harder to achieve? Why?
4) What is the difference between procedural and nonprocedural DMLs?
5) Discuss the different types of user-friendly interfaces and the types of users
who typically use each.
6) With what other computer system software does a DBMS interact?
7) What is the difference between the two-tier and three-tier client/server
architectures?
8) Discuss some types of database utilities and tools and their functions.

Unit-1: Introduction To Database: Project Presentation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit-1: Introduction To Database: Project Presentation

Uploaded by

Copyright:

Available Formats

Project Presentation

DISADVANTAGES OF FILE APPROACH

A database management system (DBMS) is a computerized system that enables users

DATABASE MANAGEMENT SYSTEMS

DATABASE MANAGEMENT SYSTEMS

A database has the following implicit properties:

WORKERS BEHIND THE SCENE

ADVANTAGES OF USING THE DBMS

DATABASE APPLICATIONS EXAMPLES

•Airlines: reservations, schedules

PURPOSE OF DATABASE SYSTEMS

PURPOSE OF DATABASE SYSTEMS (CONT.)

Database systems offer solutions to all the above

UNIVERSITY DATABASE EXAMPLE

UNIT – 2 Database System

Data Models (continued)

Categories of Data Models

•Here ID,name,dept_name and salary

On the other hand, logical data independence is harder

Hierarchical Data Model:

You might also like