A comparative analysis of data redundancy and execution time between relational and object oriented schema table

The design of database is one of the important parts in building software, because database is the data storage inside the system. There are some techniques that allow the programmer to improve design of the database. One of the most popular techniques being used for database is the relational technique, which content entity relationship diagram and normalization. The relational technique is easy to use and useful for reducing data redundancy because the normalization technique solves the data redundancy by applying normalization normal forms on the schema tables. The second technique is the object oriented technique, which content class diagram and generate schema table. An advantage of object oriented technique is its closeness to programming languages like C++ or C#. This project is starting with applying relational technique and object oriented technique to define which technique uses less data redundancy during design database. Based on experimental results for total data redundancy in HMS case study was 336 for relational technique and 364 for object oriented technique as well as, course database case study was 186 for relational technique and 204 for object oriented technique. Also, this project is focus on query execution time between relational databases and object oriented database by using user friendly window. The experimental result for query execution time in HMS case study was 107.25 milliseconds for RDBMS and 80.5 milliseconds for OODBMS. In course database case study was 46.75 milliseconds for RDBMS and 31.75 milliseconds for OODBMS. However, the comparative analysis in this project is explaining the result of comparison between relational and object oriented techniques specifically with data redundancy and query execution time

Proposed Framework which Uses Object Oriented Principles in Relational Systems: Structure and Formating (Part 2)

Our approach tries to overcome the limitations of so called “flat nature” of relational systems, in the actual context of actual relational database theories, database systems technologies and object oriented methodologies by proposing an MDA framework to map an object oriented (UML formalized) model to object-relational structures of today’s database systems

Proposed Framework which Uses Object Oriented Principles in Relational Systems: Structure and Formating (Part 2)

Our approach tries to overcome the limitations of so called “flat nature†of relational systems, in the actual context of actual relational database theories, database systems technologies and object oriented methodologies by proposing an MDA framework to map an object oriented (UML formalized) model to object-relational structures of today’s database systems.relational data structures design, object oriented principles, SQL3, UML, MDA.

Translating Relational Conceptual Schema to Object-Oriented Schema

A multidatabase is a confederation of preexisting distributed, heterogeneous, and autonomous database system. The integration process is essential in the effort of forming a distributed, heterogeneous database system. This process generally consists of two main phases, which are conceptual schema translation phase and followed by the integration phase. In our research, we have proposed an alternative translation approach to convert relational database schema to object--oriented database schema. The translation approach consists of a set of translation rules, which are based on inclusion dependencies, key attributes and types of attributes. A database schema translation tool prototype, called RETOO (Relational-to-Object-Oriented) is then developed based on the proposed translation approach. RETOO receives a relational database schema as input data and generate an object-oriented database schema as the output data.RETOO operates semi-automatically, especially in the process of identifying operations for each class. This is because relational data model does not provide the behavioural information of every entity. The translation approach and RETOO database translation tool prototype are not only able to maintain the semantics of the relational database schema, but also enhance the semantics of the translated object-oriented schema via object-oriented data modelling concepts

Object-oriented querying of existing relational databases

In this paper, we present algorithms which allow an object-oriented querying of existing relational databases. Our goal is to provide an improved query interface for relational systems with better query facilities than SQL. This seems to be very important since, in real world applications, relational systems are most commonly used and their dominance will remain in the near future. To overcome the drawbacks of relational systems, especially the poor query facilities of SQL, we propose a schema transformation and a query translation algorithm. The schema transformation algorithm uses additional semantic information to enhance the relational schema and transform it into a corresponding object-oriented schema. If the additional semantic information can be deducted from an underlying entity-relationship design schema, the schema transformation may be done fully automatically. To query the created object-oriented schema, we use the Structured Object Query Language (SOQL) which provides declarative query facilities on objects. SOQL queries using the created object-oriented schema are much shorter, easier to write and understand and more intuitive than corresponding S Q L queries leading to an enhanced usability and an improved querying of the database. The query translation algorithm automatically translates SOQL queries into equivalent SQL queries for the original relational schema

A Methodology for Reengineering Relational Databases to an Object-Oriented Database

This research proposes and evaluates a methodology for reengineering a relational database to an object-oriented database. We applied this methodology to reengineering the Air Force Institute of Technology Student Information System (AFITSIS) as our test case. With this test case, we could verify the applicability of the proposed methodology, especially because AFITSIS comes from an old version of Oracle RDBMS. We had the opportunity to implement part of the object model using an object-oriented database, and we present some peculiarities encountered during this implementation. The most important result of this research is that it demonstrated that the proposed methodology can be used for reengineering an arbitrarily selected relational database to an object-oriented database. It appears that this approach can be applied to any relational database

Object Oriented Database Management Systems-Concepts, Advantages, Limitations and Comparative Study with Relational Database Management Systems

Object Oriented Databases stores data in the form of objects. An Object is something uniquely identifiable which models a real world entity and has got state and behaviour. In Object Oriented based Databases capabilities of Object based paradigm for Programming and databases are combined due remove the limitations of Relational databases and on the demand of some advanced applications. In this paper, need of Object database, approaches for Object database implementation, requirements for database to an Object database, Perspectives of Object database, architecture approaches for Object databases, the achievements and weakness of Object Databases and comparison with relational database are discussed

Comparative Analysis of Data Redundancy and Execution Time between Relational and Object-Oriented Schema Table

Database design is one of the important phases in designing software because database is where the data is stored inside the system. One of the most popular techniques used in database design is the relational technique, which focuses on entity relationship diagram and normalization. The relational technique is useful for eliminating data redundancy because normalization produces normal forms on the schema tables. The second technique is the object-oriented technique, which focuses on class diagram and generating schema tables. An advantage of object-oriented technique is its close implementation to programming languages like C++ or Java. This paper is set to compare the performance of both relational and object-oriented techniques in terms of solving data redundancy during the database design phase as well as measuring query execution time. The experimental results based on a course database case study traced 186 redundant records using the relational technique and 204 redundant records when using the object-oriented technique. The query execution time measured was 46.75ms and 31.75ms for relational and object-oriented techniques, respectively

The advantages and cost effectiveness of database improvement methods

Relational databases have proved inadequate for supporting new classes of applications, and as a consequence, a number of new approaches have been taken (Blaha 1998), (Harrington 2000). The most salient alternatives are denormalisation and conversion to an object-oriented database (Douglas 1997). Denormalisation can provide better performance but has deficiencies with respect to data modelling. Object-oriented databases can provide increased performance efficiency but without the deficiencies in data modelling (Blaha 2000). Although there have been various benchmark tests reported, none of these tests have compared normalised, object oriented and de-normalised databases. This research shows that a non-normalised database for data containing type code complexity would be normalised in the process of conversion to an objectoriented database. This helps to correct badly organised data and so gives the performance benefits of de-normalisation while improving data modelling. The costs of conversion from relational databases to object oriented databases were also examined. Costs were based on published benchmark tests, a benchmark carried out during this study and case studies. The benchmark tests were based on an engineering database benchmark. Engineering problems such as computer-aided design and manufacturing have much to gain from conversion to object-oriented databases. Costs were calculated for coding and development, and also for operation. It was found that conversion to an object-oriented database was not usually cost effective as many of the performance benefits could be achieved by the far cheaper process of de-normalisation, or by using the performance improving facilities provided by many relational database systems such as indexing or partitioning or by simply upgrading the system hardware. It is concluded therefore that while object oriented databases are a better alternative for databases built from scratch, the conversion of a legacy relational database to an object oriented database is not necessarily cost effective

Developing Translation Rules for Converting Relational to Object Oriented Database Conceptual Schema

A multidatabase is a confederation of pre-existing distributed, heterogeneous, and autonomous database system. Obviously, the integration process is essential in the effort of forming a distributed, heterogeneous database system. This process generally consists of two main phases, which are conceptual schema translation phase followed by the integration phase. This paper presents a translation approach to convert relational database schema to object-oriented database schema. The translation approach consists of a set of translation rules, which is based on inclusion dependencies, key attributes and types of attributes. A database schema translation tool prototype, called RETOO (RElational-ToObject- Qriented) is then developed based on the proposed translation approach. RETOO receives a relational database schema as input data and generates an object-oriented database schema as the output. The translation approach is not only able to maintain the semantics of the relational database schema, but also enhance the semantics of the translated object-oriented schema via objectoriented data modeling concepts