RelationalDatabase1

Tuesday, May 30, 2006

DBMS Functions

Functional Functions...
  • Data storage, retrieval and update (physilitates users doing these)
  • User accessible catalog (catalog w/ descriptions of data items accessible by users)
  • Transaction support (mechanism that ensures all or no updates are made from a transaction)
  • Concurrency control services (mechanism that makes sure the DB is updated correctly when multi users are using the DB at the same time)
  • Recovery services (mechanism for recovering the DB if it's damaged)
  • Authorization services (mech that ensures only authorized users can access the DB)
  • Support for data communication (DB has to have a means of working with communication software)
  • Integrity services......................

3 level archictecture



logical data independence: Adding or removing new entities, attributes, or realationships shouldn't mess with existing external schema's or make changing applications necessary.

physical data independence: Changing the internal schema should be possible with out changing the conceptual/external schemas.



Referential Integrity: If a foriegn key exists in a relation the value of teh foreign key must match the candidate dey in the home relation.

Entity Integrity: In a base relation no attribute of a primary key can be null.

Data Definition Language: Describes + names entities attributes and relationships plus associated integrity and security constraints.

Data Manipulation Language(DML): Provides a set of operations to support the basic data manipulation operations (inserting, modifying, retrieving, and deleting data) on the database.

Procedural DML: Lets the user state what data is needed and how to get it.

Non procedural DML: Lets the user state what data is needed, but not how to get it.

Sunday, May 28, 2006

ER Modeling (Ch 11)

Definitions:


Relationships
--------------------------------------------------------------

Entity type: A group of objects with the same properties, which are identified by the enterprise as having an independent existence.

Entity Occurence: A uniquely identifiable object of and entity type.

Relationship Type: A set of meaningful associations among entity types.

Relationship Occurence: A uniquely identifiable association, which includes one occurence from each participating entity type.

Degree: (of a relationship) The number of participating entity types in a relationship.

Recursive relationship: A relationship type wher the same entity type participates more than once in different roles.


Attributes
------------------------------------------------------------------

Attribute: A property of a relationship type.

Attribute domain: the set of allowable values for one or more attributes.

Simple attribute: An attribute composed of a single component with an independent existence.

Composite attribute: An attribute composed of multiple components, each with an independent existence.

Single valued attribute: An attribute that holds a single value for each occurence of an entity type.

Multi-valued attribute: An attribut that holds multiple values for each occurence of an entity type.

Derived attribute: An attribute that represents a value that is derivable from the value of a related attribute or set of attributes, not necessarily in the same entity type.


Keys
-----------------------------------------------

Candidate key: The minimal set of attributes that uniquely identifies each occurence of an entitye type.

Primary key: The candidate key that is selected to uniquely identify each occurence of an entity type.

Composite key: A candidate key that consists of 2 or more attributes.


Entity Types
---------------------------------------------------

Strong Entity Type
: An entity type that is not existence-dependent on som other entity type.

Weak Entity Type: An entity type that is existence-dependent on some other entity type.


Structural Constraints
---------------------------------------------------

Multiplicity
: The number (or range) of possible occurences of an entity ype that may relate to a single occurrence of an associated entity type thru a particular relationship.

Multiplicity (complex relationship): The number (or range) of possible occurrences of an entity type in an n-ary relationship when the other (n-1) values are fixed.

Cardinality: Describes the maximum number of possible relationship occurrences for an entity participating in a given relationship type.

Participation: Determines whether all or only some entity occurrences participate in a relationship.


ER Model Problematics
---------------------------------------------------

Fan Trap: Where a model represents a relationship between entity types, but the pathway between certain entity occurrences is ambiguous.

Entity Relationship Modeling

take this short quiz...