=====
CS 325 - Week 2 Monday lecture - 2021-08-30
=====

=====
TODAY WE WILL
=====
*   announcements
*   introduce database processing and development
*   prep for next class

=====
ANNOUNCEMENTS
=====
*   today's reading was DB Reading Packet 1 - DB Processing and
    Development

*   we'll be continuing covering some material from SQL reading
    packet 1 definitely on Friday, maybe in Week 2 asynchronous
    material;

*   CLICKER QUESTIONS for POINTS START TODAY!

*   Should be working on Homework 1!
    *   Problems 1 and 2 are completed on Canvas

    *   Problems 3 onward are completed on nrs-projects,
        and submitted on nrs-projects, ~st10/325submit

    *   due 11:59 pm Friday, September 3rd

=====
Database processing and development...

*   picking up from Week 1 Asynchronous material...

*   a DBMS, then, manages the database structure,
    controls access to the data stored in the db,
    and provides various tools to allow users/application programs to use
        the data

*   what do we mean (in this course) by database design?
    *   it is not how the DBMS is built, nor is it the file
        details about how the DBMS implements a database;

    *   we mean, instead, what tables we choose to create as
        part of a database? how are they interrelated? what are
	their columns?

        ^ this is what I mean, in the DB Reading Packet 1, by
	"the design of the database structure that will be used
	to store and manage data"

    *   with these powerful DBMSs, why do we care about database
        design?

        a wonderful DBMS does not mean that you can't build a database
	using it that will NOT work well for users and applications...

        Even a good DBMS will perform poorly with a badly-designed db

        *   we'll be talking about what we might mean by
	    a "badly-designed" or "well-designed" database;

BUT before we start that -- a little history!!

*   important LIMITATIONS of file-processing systems
    as the quantity of data involved increases:
    *   separated and isolated data
    *   (unecessary) data duplication
    *   application program dependency
    *   difficulty of representing data in the users' perspective

*   these helped fuel a desire for something better!
    ...database processing systems;

*   seeking to IMPROVE on the situation, at least potentially
    *   potential for more-integrated data
    *   potential for less unnecessary data duplication
    *   potential for decreased application program dependency
    *   potential for easier representation of the user's
        perspectives

*   obviously, a database-processing approach CAN have
    disadvantages, also;