|Lesson 3 ||Database system role in an organization|
|Objective||Differentiate between DBMS types. |
Role of a Database System in an Organization
If all we need to do is keep information around and prevent it from vanishing when we turn off our computers, we could just simply put in a file on a hard drive.
If we were delivering newspapers, we might start out needing only a list of the addresses of where to deliver the papers.
However, if our needs expanded for instance, if we wanted names and payment information as well as delivery addresses,
we would begin to see the need for more sophisticated data management.
This is where database systems have a role, as they help us organize the information we collect.
The first of three main database architectures is the relational database.
The vast majority of databases are of this sort.
Relational databases store data in a row and column model, much like a spreadsheet.
The individual columns are called fields, and the rows are called records.
The entire collection of rows is usually referred to as a table. A new language, Structured Query Language
(SQL and pronounced "see-quil"), was created for working with this relational way of modeling data.
The second major type of DBMS is object-oriented. This type stores objects rather than records.
The objects it stores are like Java classes, a combination of both data and methods for manipulating that data.
This is very different than the relational approach, where you only store the data, and the manipulation of that data is left to a procedural process.
The object-oriented type of DBMS is typically not supported by JDBC.
The third type of database is a hybrid of the previous two, called an object-relational database.
It combines characteristics of both.
Like relational systems, it might support the SQL language, and like object-oriented systems, it allows for the storage of objects.
Often, relational database vendors will create extensions to their systems to support storing objects.
Again, JDBC is largely oriented to the relational model.
Vendor-specific extensions might allow an application to support these object-oriented features, but, as such,
those features are not portable across every DBMS.
The following SlideShow illustrates the various databases and their functions.