trends in the database
TRANSCRIPT
Z
Week8:Trends in Database
ManagementSubject Code: COMP131
By: Marlon JameraEmail: [email protected]
Z
Trends in Database Management
Z
Review: Trends in DatabaseManagement
• Used to manage dynamic data in real
time and stores information about the
activities of an organization.
a. Operational Database
b. Analytical Database
c. Data Warehouse
d. Distribution Database
Z
Review: Trends in DatabaseManagement
• It is designed to support business
intelligence and analytic applications,
typically as part of data warehouse or data
mart.a. Operational Database
b. Analytical Database
c. Data Warehouse
d. Distribution Database
Z
Review: Trends in DatabaseManagement
• It stores current and historical data and
are used for creating analytical reports for
knowledge workers through the
enterprise.a. Operational Database
b. Analytical Database
c. Data Warehouse
d. Distribution Database
Z
Review: Trends in DatabaseManagement
• It organizes data by column instead of rows – thus reducing the number of data elements that typically have to be ready by the database engine while processing queries.
a. Columnar Database
b. Data Warehouse Appliance
c. In Memory Database
d. MMP Database
Z
Review: Trends in DatabaseManagement
• It combines the databases with hardware and BI tools in an intelligent platform that’s turned for analytical workloads and designed to be easy to install and operate.
a. Columnar Database
b. Data Warehouse Appliance
c. In Memory Database
d. MMP Database
Z
Scope of the Lesson
• Trends in Database Management
• Embedded Database
• Document Oriented Database
• Graph Database
• Hypermedia Database
• Flat File Database
Z
Learning Outcomes
By the end of the lesson, you will be familiar with the current trends in the database.
• Define and explain perception of the embedded database
• Identify and compare the dynamics of the document oriented database and graph database
• Describe the features and the aim of the hypermedia database and a flat file.
Z
Embedded Database
• Embedded Database: these databases consist of data developed by individual end-users. Examples of these are collections of documents, spreadsheets, presentations, multimedia and other files.
Z
Embedded Database
Z
Document Oriented Database
• Document Oriented Database: the document oriented database is a computer program designed for storing, retrieving, and managing document oriented or semi structured data information.
Z
Document Oriented Database
Z
Graph Database
• Graph Database: is a kind of No SQL database that uses graph structures with nodes, edges and properties to represent and store information.
Z
Graph Database
• Graph Database: Example
Z
Hypermedia Database
• Hypermedia Database: is a computer information retrieval system that allows a user to access and work on audio-visual recordings, text, graphics and photographs of a stored subject.
• The world wide web is a perfect example of a hypermedia database.
Z
Hypermedia Database
• Hypermedia Database: Example
• The biggest advantage of hypermedia databases as compared to traditional databases is that documents are accessed via organized links. Examples of hypermedia database products in today’s market are Visual FoxPro and FileMaker Developer. These brands of software are excellent for creating business and management content.
Z
Hypermedia Database
• Hypermedia Database: Example
• The Web is a type of hypermedia database because it provides results for all available media of a phenomenon. For example, if a user types the word "vehicle" on a search engine, it gives results of various media that "vehicle" falls under. Records of items are stored according to the subject of the file.
Z
Flat File Database
• Flat File Database: is a database which, when not being used is stored on its host computer system as ordinary, non-indexed flat file.
• To access the structure of the data and manipulate it, the file must be read in its entirety into the computer’s memory.
Z
Advantages ofFlat File Database
• Placing data in flat file database has the following advantages:
• All records are stored in one place.
• Easy to understand
• Easy to set up using a number of standard office applications.
• Simple sorting of records can be carried out.
Z
Disadvantages ofFlat File Database
• Flat file has serious disadvantages when it comes to more than a few thousands of records.
Z
Disadvantages ofFlat File Database
• Potential Duplication: As more and more records are added to the database, it becomes difficult to avoid duplicate records.
• Non-unique Records: Notice that Mr. & Mrs. Jones have identical ID's. This is because the person producing this database decided they may want to sort on identical telephone numbers and so has applied identical ID to the two records. This is fine for that purpose, but supposes you only wanted to extract Mrs. Jones' record. Now it is much more difficult.
Z
Disadvantages ofFlat File Database
• Harder to Update: suppose that this is a flat file database also stored their work place details – this will result in multiple records for each person. Again, this is fine but suppose Sandra Jones now wanted to be known as “Sandra Thompson” after re-marrying? This will have to be done over potentially many records and so flat file updates are more error prone than other methods.
Z
Disadvantages ofFlat File Database
• Inherently inefficient: consider a situation where the database now needs to hold an extra field to hold an email address. If there are tens of thousands or records, there may be many people having no email address, but each record in a flat file database has to have the same fields, whether they have used or not. Other methods avoid this wasted storage.
Z
Disadvantages ofFlat File Database
• Harder to Change Data Format: Suppose the telephone numbers now have to have a dash between the area code and the rest of the number, like this 0223-44033. Adding that extra dash over tens of thousands of records would be a significant task in a flat file database.
Z
Disadvantages ofFlat File Database
• Poor at Complex Queries: If we wanted to find all records with a specific telephone number, this is a simple single-field criterion that a flat file can easily deal with. But now suppose we wanted all people living in Hull who share the same surname and similar postcode? - the criteria can quickly become too complex for a flat file to manage.
Z
Disadvantages ofFlat File Database
• Poor at Limiting Access: Suppose this flat file database held a confidential field in each record that only certain staff are allowed to see - perhaps salaries. This is difficult to achieve in a flat file database - once a person has entered a valid password to gain access, that person is able to see everything.
Z
Let’s call it a day,Thank you!