Download Agenda

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Entity–attribute–value model wikipedia , lookup

SQL wikipedia , lookup

Oracle Database wikipedia , lookup

Extensible Storage Engine wikipedia , lookup

Microsoft Access wikipedia , lookup

Concurrency control wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Functional Database Model wikipedia , lookup

Clusterpoint wikipedia , lookup

Database wikipedia , lookup

Relational model wikipedia , lookup

Open Database Connectivity wikipedia , lookup

Database model wikipedia , lookup

Transcript
Class 4 Agenda

Database Management Systems

Chapter 4: Moore’s Law

Midterm Case
Database Management
Systems: What?

Software that owns and manages data

Two models
– Relational DBMS
– Object-oriented DBMS

Provides “Storage” layer to applications

Can provide logic (constraints) to
applications
Database Management
Systems: Why?





Insulate users from data mechanics
Ensure business rules are
universally applied
Allow simultaneous access
Increase granularity of access
Standardize access language (SQL)
Database Management
Systems: Who?

Oracle

Microsoft: SQLServer

IBM: UDB / DB2

Open Systems: MySQL, PostGres, …

CA, Sybase, …
The DBMS Server layers
DBMS Client
DBMS Server
Application
Heavy Client
(Sqlplus)
App Server
Web Server
(isqlplus)
Server
Instance
Schema
DBMS Storage
Database
Instance
Schema
Schema
“Connects”
“Mounts”
Tablespace
Table
Tablespace
Table
Table
DBMS Functions

Data Integrity
– Accurate and reliable

Access Control
– Views
– Grants
– Multiple levels of access

DataAccess API
– Single well-known interface

Single point of control
– DBMS Owns the files

Utilities
Data Integrity

Locking
– Allows simultaneous use
– Different levels available

Constraints
– Limits on acceptable entries
– Discussed in detail later

Logging
– Undoing failed work
– Recording completed work
Access Control

Support for users and roles

Granularity for data (Views)
– Vertical
– Horizontal

Granularity for Function
– Read vs change
– Procedural access only
SQL API

Defines the access syntax

Open Standard

Extensions for each vendor
Relational DBMS Concepts

Value-based relations

Joins

Tables and Views

Set Processing
Object-Oriented DBMS’s
Purpose: Make storage a
service
 Classes and Objects

– Basic logic joined to data
Object “behavior”
 Behavior request mechanism
(messages)

Object-Oriented DBMS
Concepts

Inheritance
– Proper scope for all data, behaviors

Encapsulation
– Inner workings hidden from users
– Focus on behavior, not process

Polymorphism
– Each class can interpret requests
Chapter 4 Comments:
Moore’s Law





Reasons for improvement
Caching
Applies to network, storage as well
Tiers of computing need
Parallel processing
Group Reviews: Moore’s Law
Pick one, 4 minute response






Impact on “cash cow” phase of
product delivery
Impact on purchasing decisions
Is it coming to an end?
Why does network speed come in
bigger increments?
The sixth wave?
Where is the most waste?
Midterm Case Introduction:
Toyota, The Big Fix

Issues
– Project Management
– Governance?
– Reporting

Assignment
– Read
– Questions on Wednesday?