Other DBMS Functionalities DBMS may additionally provide: Protection or Security measures to prevent unauthorized access “Active” processing to take internal actions on data Presentation and visualization of data Maintenance of the database and associated programs over the lifetime of the database application
Application Programs and DBMS Applications interact with a database by generating - Queries: that access different parts of data and formulate the result of a request - Transactions: that may read some data and “update” certain values or generate new data and store that in the database
Example of a Database (with a Conceptual Data Model) Mini-world for the example: Part of a UNIVERSITY environment Some mini-world entities: STUDENTs COURSEs SECTIONs (of COURSEs) (Academic) DEPARTMENTs INSTRUCTORs
Example of a Database (with a Conceptual Data Model) Some mini-world relationships: SECTIONs are of specific COURSEs STUDENTs take SECTIONs COURSEs have prerequisite COURSEs INSTRUCTORs teach SECTIONs COURSEs are offered by DEPARTMENTs STUDENTs major in DEPARTMENTs
Note: The above entities and relationships are typically
expressed in a conceptual data model, such as the ENTITY-RELATIONSHIP data model (see Chapters 3, 4)
Main Characteristics of the Database Approach Self-describing nature of a database system: A DBMS catalog stores the description of a particular database (e.g. data structures, types, and constraints) The description is called meta-data*. This allows the DBMS software to work with different database applications. Insulation between programs and data: Called program-data independence. Allows changing data structures and storage organization without having to change the DBMS access programs
Main Characteristics of the Database Approach (continued) Data Abstraction: A data model is used to hide storage details and present the users with a conceptual view of the database. Programs refer to the data model constructs rather than data storage details Support of multiple views of the data: Each user may see a different view of the database, which describes only the data of interest to that user.
Main Characteristics of the Database Approach (continued) Sharing of data and multi-user transaction processing: Allowing a set of concurrent users to retrieve from and to update the database. Concurrency control within the DBMS guarantees that each transaction is correctly executed or aborted Recovery subsystem ensures each completed transaction has its effect permanently recorded in the database OLTP (Online Transaction Processing) is a major part of database applications. This allows hundreds of concurrent transactions to execute per second.
Database Users Users may be divided into Those who actually use and control the database content, and those who design, develop and maintain database applications (called “Actors on the Scene”), and Those who design and develop the DBMS software and related tools, and the computer systems operators (called “Workers Behind the Scene”).
Database Users – Actors on the Scene Actors on the scene Database administrators: Responsible for authorizing access to the database, for coordinating and monitoring its use, acquiring software and hardware resources, controlling its use and monitoring efficiency of operations. Database designers: Responsible to define the content, the structure, the constraints, and functions or transactions against the database. They must communicate with the end-users and understand their needs.
Database End Users Actors on the scene (continued) End-users: They use the data for queries, reports and some of them update the database content. End-users can be categorized into: Casual: access database occasionally when needed Naïve or Parametric: they make up a large section of the end-user population. Users of Mobile Apps mostly fall in this category Bank-tellers or reservation clerks are parametric users who do this activity for an entire shift of operations. Social Media Users post and read information from websites
Database End Users (continued) Sophisticated: These include business analysts, scientists, engineers, others thoroughly familiar with the system capabilities. Many use tools in the form of software packages that work closely with the stored database. Stand-alone: Mostly maintain personal databases using ready-to-use packaged applications. An example is the user of a tax program that creates its own internal database. Another example is a user that maintains a database of personal photos and videos.
Additional Implications of Using the Database Approach Potential for enforcing standards: This is very crucial for the success of database applications in large organizations. Standards refer to data item names, display formats, screens, report structures, meta-data (description of data), Web page layouts, etc. Reduced application development time: Incremental time to add each new application is reduced.
When not to use a DBMS When no DBMS may suffice: If there are stringent real-time requirements
that may not be met because of DBMS
overhead (e.g., telephone switching systems) If the database system is not able to handle the complexity of data because of modeling limitations (e.g., in complex genome and protein databases) If the database users need special operations not supported by the DBMS (e.g. location based services).
that will be used to store and manage end-user data Well-designed database Facilitates data management Generates accurate and valuable information Poorly designed database causes difficult-to- trace errors