Professional Documents
Culture Documents
1/10/2013
Database System Concepts 1.1
Last Class
n Database applications n File system versus DBS H Data redundancy and inconsistency H Difficulty in accessing the data H Data isolation H Integrity constraints H Atomicity H Concurrency control H Security
1.2
Shubhangi G.
Levels of Abstraction
n Physical level describes how a record (e.g., customer) is stored. n Logical level: describes data stored in database, and the
relationships among the data. type customer = record name : string; street : string; city : integer; end;
n View level: application programs hide details of data types.
Views can also hide information (e.g., salary) for security purposes.
1.3
Shubhangi G.
View of Data
An architecture for a database system
1.4
Shubhangi G.
H e.g., the database consists of information about a set of customers and accounts and the relationship between them) H Analogous to type information of a variable in a program H Physical schema: database design at the physical level H Logical schema (Conceptual schema) : database design at the logical level
n Instance the actual content of the database at a particular point in time
1.5
Shubhangi G.
Data independence
n Physical Data Independence the ability to modify the physical
1.6
Shubhangi G.
Database Users
n Users are differentiated by the way they expect to interact with
the system
n Application programmers interact with system through DML
calls
n Sophisticated users form requests in a database query
language
n Specialized users write specialized database applications that
1.7
Shubhangi G.
Database Administrator
n Coordinates all the activities of the database system; the
database administrator has a good understanding of the enterprises information resources and needs.
n Database administrator's duties include:
H Schema definition H Storage structure and access method definition H Schema and physical organization modification H Granting user authority to access the database H Specifying integrity constraints H Monitoring performance and responding to changes in requirements H Periodic backup H Recovery of database in case of crash
1.8
Shubhangi G.
1.9
Shubhangi G.
Application Architectures
Two-tier architecture: E.g. client programs using ODBC/JDBC to communicate with a database Three-tier architecture: E.g. web-based applications, and applications built using middleware
1.10
Shubhangi G.