DBMS Concepts


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

DBMS Concepts

  1. 1. Database Management Concepts Ch 17 – syllabus 14.3 We have already covered normalisation at the end of LVI Please recap these notes
  2. 2. The purpose of a Database Management System (DBMS) <ul><li>Storage of data </li></ul><ul><li>In separate tables with linked fields </li></ul><ul><li>Within the structure of database or data dictionary. </li></ul><ul><li>Provides interface between user and data </li></ul><ul><li>And allows data to be queried </li></ul><ul><li>And allows construction of reports. </li></ul><ul><li>It also controls access to the data/security </li></ul>
  3. 3. How a DBMS can help consolidate data from several different places <ul><li>Provides a buffer between the user and the underlying structure of the database so the user is not concerned with the structure of the database, just with making relevant use of the data </li></ul><ul><li>Can be used to create a consistent database with a consistent interface so if users move from one location to another they already know how to use the system </li></ul><ul><li>RDBMS will control access to data so all places will see the most up to date data </li></ul><ul><li>In event of disaster, RDBMS should help with disaster recovery e.g. provide ability to consolidate data and roll back to a known correct state </li></ul><ul><li>RDBMS may provide improved security to the system so that there is less chance of inexperienced users inadvertently changing data or malicious attempts to corrupt data succeeding </li></ul>
  4. 4. The role of a Database Administrator <ul><li>D esigns the database by setting up appropriate tables, relationships, fields, naming conventions etc. </li></ul><ul><li>A llocation of data access to users including access rights, providing user names </li></ul><ul><li>M aintains the data dictionary i.e. the data structure </li></ul><ul><li>P rovides training to users as appropriate so new users learn how to use the system, and existing users get updates as necessary </li></ul><ul><li>M onitors the performance of the RDBMS and makes appropriate adjustments to deal with problems as they arise e.g. system taking too long to produce a report </li></ul><ul><li>I n charge of the backup procedure and ensures the database is available to users at the times that they need it </li></ul><ul><li>N otify users of any changes so that they can make changes to the way they use the database appropriately e.g. availability of new reports/ queries </li></ul>DAMPMIN
  5. 5. Data Consistency <ul><li>Data is stored as one value, and not stored again as another value. </li></ul><ul><li>EG if Gayle Robinson’s name is stored in one table, then stored as Gail Robinson in another table this data would be inconsistent. </li></ul><ul><li>Consistency comes with reduced redundancy where data is only stored once, and this is the sole source of that data. </li></ul>
  6. 6. Data Integrity <ul><li>Is the correctness of the data or how trustworthy the data is. </li></ul><ul><li>It should be free from corruption and validated whenever it is transferred from one medium to another. </li></ul><ul><li>EG Validation of data such as range check on an amount of currency as it is typed from a data capture form to a RDBMS </li></ul><ul><li>EG Parity check of data as it is sent over a telecommunications link. </li></ul>Not corrupted
  7. 7. Data Redundancy <ul><li>Data is stored as one value in many places </li></ul><ul><li>EG Lauren Carpenter’s name and contact details are stored in the personnel table, and her name and contact details are also stored in the payroll table. </li></ul><ul><li>Redundancy means data is more likely to be inconsistent as any changes to one data item must be made manually to all its occurrences. </li></ul><ul><li>A RDBMS reduces redundancy by creating a unique key field EG PersonID to replace duplicate details in other tables. </li></ul>
  8. 8. Data Independence <ul><li>Data tables are separate from the programs/functions that use them </li></ul><ul><li>EG the same table may have two or more different views: the delivery function can see customer name and address only; however the credit control function can see the customer income, credit history, and contact details </li></ul><ul><li>Changes in the structure of the data tables only affects those programs/ functions that are reliant on that part of the structure </li></ul><ul><li>EG the introduction of a new field to a table only needs changes made to the functions that will use the field and not to all the functions that use the table. </li></ul>
  9. 9. Data Normalisation <ul><li>Process of breaking down complex data structures into simpler forms </li></ul><ul><li>(1NF) Removal of repeating fields </li></ul><ul><li>(2NF) Removal of composite keys/partial key dependencies </li></ul><ul><li>(3NF) Removal of non-key dependencies </li></ul><ul><li>Normalisation is the process for making the structure of a relational database more efficient by defining tables, fields, and relationships to minimise duplication of data and increase data consistency. Data integrity is assured by data validation specified in the data dictionary. Complex queries are also achieved using efficient relationships between tables. </li></ul>
  10. 10. DBMS Jargon <ul><li>Entity (Table/Record) ; Person / place / thing about which data is stored e.g. patient </li></ul><ul><li>Attribute (Field) ; Property associated with the entity e.g. patient’s blood group </li></ul><ul><li>Relationship ; Link between entities e.g. patient can have one ward but one ward can have many patients. This is a one to many relationship. </li></ul>
  11. 11. Entity Relationship Diagrams <ul><li>Provide a diagrammatic representation of the structure of the data and shows the types of relationships within the database. The relationships include: </li></ul><ul><ul><li>one to one (not common) </li></ul></ul><ul><ul><li>one to many (common) </li></ul></ul><ul><ul><li>many to many (not physically possible) better to have: </li></ul></ul>
  12. 12. The Nature of a Client/Server Database System (P210) <ul><li>Client Computer: A local workstation that just provides the user interface to request data queries/reports from the server </li></ul><ul><li>Server Computer : A remote computer where the processing is carried out to provide the query results/reports to the client computer. The server computer is more powerful than the client computer because it has to contain the whole RDBMS. </li></ul><ul><li>The advantages of a client/server database system </li></ul><ul><li>cost-effective: clients are cheaper than servers so this expensive resource is made available to a large user base </li></ul><ul><li>• data consistency is maintained as one copy of data is held on the server, rather than a copy held on each workstation </li></ul><ul><li>• communication between client & server is minimal as only requests/results are communicated, not entire databases </li></ul><ul><li>• Department specific report formats or queries can be held on workstations meaning less room is taken up on the server and they are less likely to be accessed by the wrong people. </li></ul>
  13. 13. The End Now do the exam questions! Do the exam questions!