BACKGROUND

1
(No Transcript)
2
BACKGROUND

• IBM DB2 is a universal database that has a long
• history and was what some consider being the
  first
• database product to use SQL. The name DB2
• was first given to the Database Management
• System or DBMS in 1982 where IBM released
• SQL/DS and DB2 on its mainframe platform.
• The first DB2 product was released in 1984 on the
• IBM mainframe platform.

3
BACKGROUND

• Prior to this the product was named System
• Relational, or System R, which launched in
• 1978. DB2 has its roots back to the
• beginning of the seventies where Dr. E.F.
• Codd who works for IBM, described the
• theory of relational databases and in June
• of 1970 published the model for data
• manipulation.

4
BACKGROUND

• To apply the model, Codd needed a
• relational database language which he
• named Structured English Query
• Language or SEQUEL. SEQUEL was
• already a trademarked name, so IBM
• renamed the acronym to SQL, short for
• Structured Query Language. The acronym
• SQL still stands to this day.

5
BACKGROUND

• In 2001 IBM bought Informix and in the
• following years incorporated Informix
• technology into the DB2 product suite.
• IMB increased its product in areas such as
• Transaction processing, Query processing,
  parallel
• processing and optimization.
• Technically today, DB2 can be considered to be an
• object-relational database. IBM DB2 software is
• modeled and specified using the Unified Modeling
• Language. (UML)

6
DB2 DIFFERENT EDITIONS

• Enterprise server edition (ESE)
• Workgroup server edition (WSE)
• Workgroup server unlimited edition
• Personal edition
• Universal developers edition
• Personal developers edition

7
DB2 supports

• JOIN
• AGGREGATION
• SET OPERATIONS
• COMPLEX SQL PROCESSING
• CONSTRAINT AND INTEGRITY
• CONCURRENCY CONTROL RECOVERY
• CONCURRENCY AND ISOLATION

8
AUTHENTICATION AND SECURITY
The DB2 UDB security model consists of two main
components
authentication and authorization
9
AUTHENTICATION

• Authentication is the process of validating a
• supplied user ID and password using a
  security
• mechanism.
• User and group authentication is managed in a
• facility external to DB2 UDB, such as the
  operating system, a domain controller, or a
  Kerberos security system.
• This is different from other database management
• systems (DBMSs), such as Oracle and SQL
  Server.

10
ERROR DETECTION
This message is returned to the application by
DB2 UDB when user authentication fails

• SQL30082N Attempt to establish connection failed
  with security
• reason "24" ("USERNAME AND/OR PASSWORD
  INVALID").
• SQLSTATE08001

11
AUTHORIZATION

• Authorization is the process of determining
  access and privilege information about specific
  database objects and actions for a supplied user
  ID.
• DB2 UDB stores and maintains user and group
  authorization information internally.
• Each time you submit a command, DB2 UDB performs
  authorization checking to ensure that you have
  the correct set of privileges to perform that
  action.
• Privileges can be granted to specific users or to
  groups of users. Again, both the user and group
  definition themselves are defined outside of DB2
  UDB.
• Users that are a member of a group automatically
  inherit the group's privileges.

12
AUTHORIZATION
Most database objects have a set of associated
privileges that can be assigned to users and
groups, using the SQL statements GRANT and
REVOKE. For example

• 1. Grant select on table Employee to user Kevin
• 2. Revoke insert on view customer from group 18
• 3. Grant select on table Machine to user xyz

13
AUTHORIZATION
14
ERROR DETECTION
If a user is not authorized to perform an
operation against a specific object, DB2 UDB
refuses the operation and returns an error
message to the client application. For example,
if the user Phillip tried to INSERT a row into
the Employee table, but did not have sufficient
privileges to do so, the following error message
would be returned
This message is returned by DB2 UDB when user
authorization fails
DB21034E The command was processed as an SQL
statement because it was not a valid Command Line
Processor command. During SQL processing it
returned SQL0551N Phillip" does not have the
privilege to perform operation "INSERT" on object
Employee". SQLSTATE42501
15
IBM DB2 ADVANTAGES

• IBM DB2 Runs on all types of platforms including
  Windows, Linux, AIX, HP-UX, Sun Solaris
• Integrated web access
• Data replication service
• Integrated system management tools
• Integrated support for complex data
• IBM program for assistance to developers

16
IBM DB2 DISADVANTAGES

• IBM DB2 is very expensive due to its different
  editions.
• The database server do not supports online
  analytical processing and Data mining
• IBM DB2 uses a lot of memory space

17
REFERENCES
Silberschatz, A (et. Al) Database Systems
Concepts http//www.databasesecurity.com/db2/secd
b2.htm http//www-128.ibm.com/developerworks/db2/
library/techarticle/dm-0512patil/ http//www-128.
ibm.com/developerworks/db2/library/techarticle/dm-
0508wasserman/index.html http//publib.boulder.ib
m.com/infocenter/db2luw/v8//index.jsp?topic/com.i
bm.db2.udb.doc/admin/c0005435.htm
18
AUTHORIZATION
19
AUTHORIZATION
20

Live Demonstrations of
Next Week Monday
Coming to a lecture theatre near you!
21

Live Demonstrations of
Next Week Monday
Coming to a lecture theatre near you!