From Conceptual Database Schemas to Logical Database Tuning

Author(s):  
Jean-Marc Petit ◽  
Mohand-Saïd Hacid

This chapter revisits conceptual database design and focuses on the so-called “logical database tuning”. We first recall fundamental differences between constructor-oriented models (like extended Entity-Relationship models) and attribute-oriented models (like the relational model). Then, we introduce an integrated algorithm for translating ER-like conceptual database schemas to relational database schemas. To consider the tuning of such logical databases, we highlight two extreme cases: null-free databases and efficient — though non redundant — databases. Finally, we point out how SQL workloads could be used a posteriori as a help for the designers and/or the database administrators to reach a compromise between these extreme cases. While a lot of papers and books have been devoted for many years to database design, we hope that this chapter will clarify the understanding of database designers when implementing their databases and database administrators when maintaining their databases.

10.28945/3199 ◽  
2008 ◽  
Author(s):  
Milos Bogdanovic ◽  
Aleksandar Stanimirovic ◽  
Nikola Davidovic ◽  
Leonid Stoimenov

Most universities where students study informational technologies and computer science have an introductory course dealing with the development and design of databases. These courses often include usage of database design tools. In this paper, the #EER tool is presented, the task of which is to make the process of relational databases design easier for the students and partially automatize it. The tool evolved due to the experience in using similar tools for educational purposes. It enables fast and efficient development of the relational database conceptual model and its automatized compilation into a relational model and further to data definition language (DDL) commands. #EER tool is based on the extended entity-relationship (EER) model for conceptual modeling of relational databases. Modular architecture of the tool, the development of which is based on the usage of the design patterns, along with the benefits that its usage brings, is also presented.


Author(s):  
Morad Hajji ◽  
Mohammed Qbadou ◽  
Khalifa Mansouri

Ontologies are spreading more and more in the field of information technologies as a privileged solution allowing the formalization of knowledge. The theoretical model of ontologies is most promising. They are increasingly ubiquitous given the benefits they present. Despite the proliferation of research proposing approaches dedicated to the design of a database from an ontology, the tools to design a database from an ontology are rare or inaccessible. Thus, in this contribution, we present our approach for the development of an Eclipse Plug-in, in order to automatically generate a conceptual model of a relational database from an ontology. To evaluate the usefulness of our approach, we used our resulting Eclipse Plug-in to automatically generate a conceptual model of a relational database from an ontology, customize it, and automatically generate the corresponding SQL script for Data Definition. The results of this experiment showed that our Plug-in constitutes a concretization of our approach and a means of automatic translation from the ontological model to the relational model.


1994 ◽  
Vol 6 (2) ◽  
pp. 71-84 ◽  
Author(s):  
James Bradley

Relational database design methodologies have recently been promoted for providing historians with a useful way of organising data within databases. This paper explores some of the problems which arise from using these methodologies, but suggests that techniques like Entity-Relationship Modelling remain intuitive and natural ways of coping with the complexities of historical data.


Author(s):  
C. David Butler

Data integrity is essential to every organization and to every healthcare practitioner in order to ensure the correct use of patient information to optimize care. It provides the assurance that the data you see every day is the same as it was the day before. It assures you that the drug dosage regimen “QID,” whether you define it as four times daily or four times daily with meals and at bedtime, is applied using the same parameters for every patient, as you define a patient, across every day (or any time period), as you define day in your health care setting. Definitions about data must be made by the business person (the practitioner), rather than by Information Technology (IT). Only by doing this can appropriate business rules by applied by a database, which manages the information used in electronic medical records. Once a decision is made about what a datum represents, whether by an individual or a group, it is imperative that the decision remain consistent over time. Should the definition evolve, it is also imperative that that evolution be tracked. Thus, organizations must establish governance committees to maintain consistency both across an organization and across time. Governance committees must have the highest level of authority to ensure that rules are not overridden on a casual, intermittent basis. Once business rules for data have been established, use of a relational database provides one of the strongest tools for ensuring that data integrity is maintained. This chapter explores the concepts serving as the foundation for today’s relational database management systems. A top-down approach is described using an Entity-Relationship diagram that can be used to create a relational model for implementation in a relational database management system. A bottom-up approach is described using functional dependencies and normalization. A pharmacist should be able to apply these concepts in corporation with a database architect to ensure the appropriate, consistent use of drug data within an organization. A pharmacist must be able to validate all drug information being used across the organization in order to minimize medication errors and optimize patient care. Only by being the subject matter expert on governance committees and working closely with IT and quality assurance can pharmacy maintain appropriate control over the use of drug information by healthcare technology.


2021 ◽  
Vol 12 (2) ◽  
Author(s):  
Ronaldo Dos Santos Mello ◽  
Carlos Henrique Cândido ◽  
Milton Bittencourt S. Neto

The brModelo tool is a initiative of the UFSC Database Group. Its first version was developed in 2005, and its main purpose is to help teaching of relational database design. Compared to similar tools, its main differentials are the support to all steps of the classical database design methodology, user interaction during the logical design step, as well as the support to all extended Entity-Relationship concepts. With more than fifteen years of existence, the brModelo was very well-accepted by the brazilian Database community, which motivated the development and release of several versions of the tool. This article presents the history of brModelo, including its available versions and their functionalities. Additionally, we detail its functionalities and compare it with popular related tools.


Sign in / Sign up

Export Citation Format

Share Document