1. Relational Database
1.1. Stores data in a collection of related tables.
1.1.1. Each table has a sequence of records, similar to that of a flat file.
1.1.1.1. Two tables can be joined by similar fields.
1.1.1.2. Tables are essentially independent, but can be joined to complete a particular task.
2. Dimensional Database
2.1. Also referred to as a multidimensional database, organizes relationships over three or more dimensions.
2.1.1. Each field is contained within a cell that can be accessed from a query or from following a relationship.
2.1.1.1. Offers a simple way to visualize data and formulate queries.
3. Object-relational Database
3.1. Used to describe a variety of technologies that combine object-oriented and related concepts. Described as an attempt to add OO-ness to tables.
3.1.1. Have the flexibility to store unique types of data and program code necessary to access that data.
3.1.1.1. For example, a relational database sends a file name to an external player, but an object-relational database can store the song data and the routine to play it. Like iTunes.
4. Flat File
4.1. Simplest model for storing data. Consists of a single, two-dimensional table of data elements.
4.1.1. Most databases display records as rows in a table or as forms.
4.1.1.1. A record refers to a collection of data fields.
4.1.1.1.1. A record has a template referred to as a record type and contains field names, but no data. Also, a data contained record is called a record occurance.
4.1.2. The smallest unit of meaningful information is called a field.
4.1.2.1. A field name is designed to describe the field's contents.
4.1.2.2. There are two types of length fields known as variable-length fields and fixed-length fields.
4.1.2.2.1. Variable-length field expands to fit the data you enter, up to a max number of characters
4.1.2.2.2. Fixed-length fields contain a predetermined number of characters.
5. Relationship Databases
5.1. Hierarchial Database
5.1.1. Allows one-to-one and many-to-many relationships
5.1.1.1. A one-to-one relationship means one record is related to many records
5.1.1.1.1. For example, in the case of a CD store, a customer can order many albums. Also, an album has only one description.
5.1.1.2. A many-to-many relationship means that one record in a specific record type can be related to many records in another record type.
5.1.1.2.1. For example, one album contains many songs, and a song can be included in a number of different albums
5.1.1.3. Rarely used in today's businesses, but are still used for specific applications.
5.2. Network Database
5.2.1. Combines both one-to-one and many-to-many
6. Object Database
6.1. Also referred to as an object-oriented database, stored data as objects, which can be grouped into classes and defined by attributes and methods.
6.1.1. Can easily store data about different types of orders.
6.1.1.1. For example, a class called orders holds data and methods common to all types of orders. A class called web orders is common to only orders placed on the web.