1 Data model: OODBMS vs. RDBMS
For this coursework two kinds of data models can be used. The object oriented data model, Object Oriented Database Management System(OODBMS), or the relational data model, Relational Database Management System(RDBMS). The differences between these two models and the data model to be used are described in this chapter.
1.1 Enumeration of some specifications of OODBMS and RDBMS
RDBMS have been around for more than 20 years, OODBMS are relatively new;
RDBMS can handle >10.000.000.000 records, OODBMS up to 10.000.000.
OODBM is good for storing complex descriptions (e.g., a plant schematic), RDMSs appropriate for simple, “flat” data.
RDBMS control the DB market (>90%), OODBMS own <5% of the market.
The relational model, as implemented in most RDBMSs, can represent a lot of different models, but has difficulty representing inheritance hierarchies, and complex relationships (many many-to-many's) are costly to process
1.2 Advantages of an OODBMS
1. Composite Objects and Relationships: Objects in an OODBMS can store an arbitrary number of atomic types as well as other objects. It is thus possible to have a large class which holds many medium sized classes which themselves hold many smaller classes, ad infinitum. In a relational database this has to be done either by having one huge table with lots of null fields or via a number of smaller, normalized tables which are linked via foreign keys. Having lots of smaller tables is still a problem since a join has to be performed every time one wants to query data based on the "Has-a" relationship between the entities. Also an object is a better model of the real world entity than the relational tuples with regards to complex objects. The fact that an OODBMS is better suited to handling complex,interrelated data than an RDBMS means that an OODBMS can outperform an RDBMS by ten to a thousand times depending on the complexity of the data being handled.
2. Class Hierarchy: Data in the real world is usually has hierarchical characteristics. The ever popular Employee example used in most RDBMS texts is easier to describe in an OODBMS than in an RDBMS. An Employee can be a Manager or not, this is usually done in an RDBMS by having a type identifier field or creating another table which uses foreign keys to indicate the relationship between Managers and Employees. In an OODBMS, the Employee class is simply a parent class of the Manager class.
3. Circumventing the Need for a Query Language: A query language is not necessary for accessing data from an OODBMS unlike an RDBMS since interaction with the database is done by transparently accessing objects.
Data provisioning stores the organizational structure regulations in tables in its database, so these regulations can be changed without any difficulties when management decides to modify the organization.
A database is a structured collection of data. Data refers to the characteristics of people, things, and events. Oracle stores each data item in its own field. For example, a person's first name, date of birth, and their postal code are each stored in separate fields. The name of a field usually reflects...
Microsoft Access is a database engine and development environment in one package. It is typically workstation-based, and designed to be easy to use, even for users with no experience. However, it also provides advanced functionality for experienced users. MySQL is the largest open-source RDMBS, and it is server-based, as well as the rest of the DBMS that will be discussed. According to the mysql.com website, it offers high reliability and performance, easy use and deployment, freedom from platform lock-in by providing ready access to source code, and cross-platform support. SQL Server is an enterprise class RDBMS from Microsoft. It is part of the Back Office Suite of products. Although it is always server-based in production, it can be client-based in development. DB2 is also an enterprise-class DBMS, produced by IBM. It offers some object-oriented functionality, as well as cross-platform compatibility, and is server-based. Finally, Oracle offers much of the same functionality as DB2, with cross-platform capability, and some object-oriented features. It, as well, is server-based.
From the scenario described above, I have determined that the following main entities are the most appropriate for a relational database: cemeteries, burial plots, burial records, monuments, buildings, and inscriptions. Each main entity and its significant attributes will be described below; however, a full list of attributes can be found in the appendix.
These structures could look similar to a relational database, but others look completely different. Depending on the specific structure used, your choice of Database Management Systems will change as well. There are four common data models to use: Key/Value Stores, Document Databases, Table-Style Databases, and Graph Databases (Data Access for Highly Scalable Solutions). Key Value Stores Looking at the different data storage models, this is the most simple to implement. This is a way to have a schema-less design for storing data.
Since the SQL language appeared in mid 1970s, it has been leading the relational database industry for many years. With the modern era of databases not everyone sees the advantages of using relational databases. NoSQL, was first developed in the twenty first century (MongoDB, para 19) to address the issues that the SQL language could not handle. NoSQL cannot handle pure relational database models, it can use any of five different kinds of models, including relational to solve problems. With the variety of models, designers are wondering if there is a future for the strictly relational language SQL, and it’s other disadvantages compared to that of NoSQL.
The Revolution in Database Architecture, by Jim Gray, describes the path that Gray thought that the evolution of the Database Architecture would take after 2004. He considers that databases had been stagnated for several years and that, beginning in 2004, the development of several technologies would pave the way into a revolution in the database world.
[7] Elmasri & Navathe. Fundamentals of database systems, 4th edition. Addison-Wesley, Redwood City, CA. 2004.
In the world of database technology, there are two main types of databases: SQL and NoSQL—or, relational databases and non-relational databases. The difference speaks to how they’re built, the type of information they store, and how they store it. Relational databases are structured, like phone books that store phone numbers and addresses.
The following diagram illustrates the structure of a typical application which accesses persistent data stored in a relational database. The data logic and JDBC API are embedded to some degree within the business logic, tightly coupling the two layers together.
Oracle is another database management system and it is one of the best. Oracle database management system was set up by the “Oracle Corporation”. Oracle Corporation is an American based computer technology corportation. In 1977, Software Development Laboratories (SDL) was set up by Larry Ellison, Bob Miner and Ed Oates. This consultancy then developed the original version of the Oracle software. “Oracle” comes from the code name of a project that Ellison had worked on a few years previous. The Oracle Relational Database Management system or Oracle RDBMS for short has had some clients find it difficult to install on Linux systems. Unlike MySQL, Oracle is not open source and can become quite pricey when dealing with a lot of database materials. Oracle would not be my first choice of RDBMS.
"Although fully searchable text could, in theory, be retrieved without much metadata in the future, it is hard to imagine how a complex or multimedia digital object that goes into storage of any kind could ever survive, let alone be discovered and used, if it were not accompanied by good metadata" (Abby Smith). Discuss Smith's assertion in the context of the contemporary information environment
Secondly is a DBMS as a storage management that create a structured required from a complex data. This way will avoid us from having a difficult way to define and programmes the information data characteristics. DBMS consist of modern DBMS that provide another function in deep compared to the common DBMS. This modern DBMS will also include related data foe entry form, or screen definitions, report definitions, data validation rules, procedural code, structures to handle video and picture formats,
Many users find it easier to install, implement and use MySQL than other RDBMS. The developers can easily install MySQL without dealing with complex configurations. At the same time, they can use a number of third-party tools to implement the database according to their requirements. Each programmer familiar with Structured Query Language (SQL) can further use the database without any hassle.
There are various terms that are associated with Enterprise Data Management. Some of these terms are UML, OLAP, OLTP, Data Warehouse, Data Mart and Multi-Tier Architecture. Subsequently, these terms were covered during the five week course of DMB405 and will be explained in further detail throughout the course of the paper. Although the paper will not be all inclusive to the detail of each term, it will touch upon the definition, their use and their place in Enterprise Data Management. The first term that will be discussed is UML and how it relates to the subject at hand.