Challenges on Modeling Hybrid XML-Relational Databases

2010 ◽  
pp. 28-45 ◽  
Author(s):  
Mirella M. Moro ◽  
Lipyeow Lim ◽  
Yuan-Chi Chang
Keyword(s):  
Relational Database ◽  
Relational Databases ◽  
Database Design ◽  
Design Guidelines ◽  
Use Cases ◽  
Future Research ◽  
Schema Evolution ◽  
Design Methodologies ◽  
Integrated Environment ◽  
Context Data

It is well known that XML has been widely adopted for its flexible and self-describing nature. However, relational data will continue to co-exist with XML for several different reasons one of which is the high cost of transferring everything to XML. In this context, data designers face the problem of modeling both relational and XML data within an integrated environment. This chapter highlights important questions on hybrid XML-relational database design and discusses use cases, requirements, and deficiencies in existing design methodologies especially in the light of data and schema evolution. The authors’ analysis results in several design guidelines and a series of challenges to be addressed by future research.

From Databases to Ontologies

2009 ◽  
pp. 2360-2383
Author(s):  
Guntis Barzdins ◽  
Janis Barzdins ◽  
Karlis Cerans
Keyword(s):  
Conceptual Model ◽  
Relational Database ◽  
Relational Databases ◽  
Database Design ◽  
Database Schema ◽  
Design Problems ◽  
Uml Profile ◽  
Domain Experts ◽  
Owl Ontology ◽  
Rdf Database

This chapter introduces the UML profile for OWL as an essential instrument for bridging the gap between the legacy relational databases and OWL ontologies. We address one of the long-standing relational database design problems where initial conceptual model (a semantically clear domain conceptualization ontology) gets “lost” during conversion into the normalized database schema. The problem is that such “loss” makes database inaccessible for direct query by domain experts familiar with the conceptual model only. This problem can be avoided by exporting the database into RDF according to the original conceptual model (OWL ontology) and formulating semantically clear queries in SPARQL over the RDF database. Through a detailed example we show how UML/OWL profile is facilitating this new and promising approach.

scholarly journals The Development and Usage of a Relational Database Design Tool for Educational Purposes

10.28945/3199 ◽  
2008 ◽  
Author(s):  
Milos Bogdanovic ◽  
Aleksandar Stanimirovic ◽  
Nikola Davidovic ◽  
Leonid Stoimenov
Keyword(s):  
Relational Database ◽  
Design Patterns ◽  
Relational Databases ◽  
Conceptual Modeling ◽  
Database Design ◽  
Design Tool ◽  
Relational Model ◽  
Modular Architecture ◽  
Data Definition ◽  
Entity Relationship

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.

Relational Database Design and the Reconstruction of the British Medical Profession: Constraints and Strategies

1994 ◽  
Vol 6 (2) ◽  
pp. 71-84 ◽  
Author(s):  
James Bradley
Keyword(s):  
Relational Database ◽  
Historical Data ◽  
Medical Profession ◽  
Database Design ◽  
Ways Of Coping ◽  
Design Methodologies ◽  
Entity Relationship

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.

scholarly journals Using the REA Data Model in Order to Reduce Design Complexity in an Inventory Management Relational Database, and the Need for a Relational Database Complexity Metric.

2021 ◽  
Vol 9 (7) ◽  
pp. 71-78
Author(s):  
Ian Adamson
Keyword(s):  
Inventory Management ◽  
Relational Database ◽  
Data Model ◽  
Relational Databases ◽  
Database Design ◽  
Business Environment ◽  
Design Complexity ◽  
Data Inconsistency ◽  
A Company

With the extensive use of relational databases in the business environment there is a need to reduce database complexity in order to avoid data inconsistency and redundancy, which can provide a company with unreliable and/or meaningless data and information. The use of the REA Data Model in database design can significantly help with this problem.  The model can eliminate the need for unnecessary data artifacts which should only be generated by the system when needed. This paper also addresses the need for a Relational Database Complexity Metric. A simple and easy to understand metric is presented.

From Databases to Ontologies

2009 ◽  
pp. 242-266 ◽  
Author(s):  
Guntis Barzdins
Keyword(s):  
Conceptual Model ◽  
Relational Database ◽  
Relational Databases ◽  
Database Design ◽  
Database Schema ◽  
Design Problems ◽  
Uml Profile ◽  
Domain Experts ◽  
Owl Ontology ◽  
Rdf Database

This chapter introduces the UML profile for OWL as an essential instrument for bridging the gap between the legacy relational databases and OWL ontologies. We address one of the long-standing relational database design problems where initial conceptual model (a semantically clear domain conceptualization ontology) gets “lost” during conversion into the normalized database schema. The problem is that such “loss” makes database inaccessible for direct query by domain experts familiar with the conceptual model only. This problem can be avoided by exporting the database into RDF according to the original conceptual model (OWL ontology) and formulating semantically clear queries in SPARQL over the RDF database. Through a detailed example we show how UML/OWL profile is facilitating this new and promising approach.

Review of Contemporary Database Design and Implication for Big Data

2021 ◽  
Vol 12 (4) ◽  
pp. 1-11
Author(s):  
Halima E. Samra ◽  
Alice S. Li ◽  
Ben Soh ◽  
Mohammed A. AlZain
Keyword(s):  
Big Data ◽  
Data Storage ◽  
Relational Database ◽  
Relational Databases ◽  
Database Design ◽  
Relevant Information ◽  
Data Modelling ◽  
Comprehensive View ◽  
High Consistency ◽  
Modelling Process

In general, databases provide a single comprehensive view suitable for analysis and relevant information for a variety of organizational purposes. The intent of this paper is to review the contemporary database design in terms of data modelling, process modelling, relational databases, and data storage. The review indicates the contemporary relational database architecture provides numerous advantages such as high consistency and availability. However, it is not suitable for big data because its performance decreases as the data grows and faces scalability constraints as it is impossible to scale horizontally, and its vertical growth is limited. An implication here is that big data requires more than a relational database and the traditional SQL.

Distributed database design methodologies

1987 ◽  
Vol 75 (5) ◽  
pp. 533-546 ◽  
Author(s):  
S. Ceri ◽  
B. Pernici ◽  
G. Wiederhold
Keyword(s):  
Database Design ◽  
Distributed Database ◽  
Design Methodologies ◽  
Distributed Database Design
Sign in / Sign up

Export Citation Format

Share Document