SILS iSchool

31 Oct 2018

Value Added | daily

Class Schedule

Basics | sessions 01-05

22 AUG | intro
27 AUG | clients
29 AUG | servers
05 Sep | networks
10 Sep | basics lab

Web Development | sessions 06-11

12 Sep | structural layer
17 Sep | presentational layer
19 Sep | working with layers
24 Sep | behavior layer
26 Sep | images & design
01 Oct | website lab

Document Markup | sessions 12-14

03 Oct | object layers
08 Oct | graphics
10 Oct | document markup lab

Spreadsheets | sessions 15-19

15 Oct | spreadsheets
17 Oct | formulas & functions
22 Oct | thoughts about data display
 18 Oct  | Fall Break 
24 Oct | database tools
29 Oct | spreadsheets lab

Relational Database | sessions 20-26

 31 Oct  |  relational databases  | Access- a RDBMS | create a database | next session

05 Nov | tables
07 Nov | relationships
12 Nov | input & output
14 Nov | SQL
19 Nov | complex queries
26 Nov | databases lab
 21 Nov | Thanksgiving 

Presentation | sessions 27-30

28 Nov | presentation design
03 Dec | presentation delivery
05 Dec | presentation lab
12 Dec | 0800-1100 | final in class presentation

A relational database is one in which you can store information in different tables,
each containing different information that relates to information in the other tables

Relational Databases


a database is a collection of related data

a database management system (or DBMS) is a system designed for two main purposes

  1. to add, delete, and update data in the database
  2. to provide various ways to view (on screen or in print) the data in the database

a flat file database is one where all the data is contained in a single table, such as in Excel

a relational database is one in which you can store information in different tables, each containing different information that relates to information in the other tables

comparing flat file databases to relational databases

back to top

Why use a relational database design?

  • to eliminate unnecessary redundancy or repetition in storage and in steps required for database maintenance
  • to be able to distribute the database to multiple locations, each with a responsibility to maintain a part of the total database

back to top

So a relational database is characterized by

  • multiple tables, perhaps maintained by multiple locations
  • with relationships defined between the tables, so that the entire distributed, relational database works together

back to top

Entity Relationship Model of a Database

an entity-relationship model (ERM) is an abstract and conceptual representation of data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion. Diagrams created by this process are called entity-relationship diagrams (or ER diagrams)

One has choices in how to model the elements in a database. One of the standard textbooks on the topic (Elmasri, R., & Navathe, S. (2011). Fundamentals of database systems. Boston: Addison-Wesley.) offers a view of the several methods.

The purpose of a database is to store information about certain types of objects.

To make the distinctions clear, we will use a color schema in which we use
terms relevant to entity relationship models
and their correlates in Access
and, when appropriate, their correlates in Excel

In database language, objects are entities;

in Access, entities are records

in Excel, entities are rows

type ⇒⇒⇒⇒⇒⇒ ⇓⇓⇓⇓⇓⇓
ERModel entity set composed of entities which have attributes
Access tables composed of records which have fields
Excel worksheets composed of rows which have column cells

An entity class [like books]

is an abstract definition of something

an entity (like a textbook for INLS161) is a concrete example of that description

in Access, an entity is a record

An entity

is composed of attributes

in Access, attributes are fields
attributes/fields include information we want in the database
attributes/fields help to uniquely identify individual entities within a class
attributes/fields can describe relationships between entities in different classes

An entity set

is the list of given entities/records within a given entity class that are currently in the database/table

in Access, an entity set is a table

back to top

Primary and Foreign Keys

a Primary Key

is a set of attributes/fields that uniquely identifies an entity/a record

a Foreign Key

is a copy of the Primary Key of one entity class/table that appears as an attribute/field in another entity class/table and helps define the relationship between entities/records in the two entity classes/tables

these keys link together the related entity sets/tables in a relational database

Access Database Design Help

back to top