Authors: Martin Steeg
Tags: 1996, conceptual modeling
Traditional database design does not consider operational behavior in detail. In this way, tuning is a frequent requirement after conceptual, logical and physical design has been finished. The intension of tuning is to make database transactions run more quickly, which often results in redesigning and/or denormalizing internal data schemata. This, however, can become a crucial part of database life cycles whenever internal views are not represented externally anymore- and vice versa. This document introduces a data modeling and behavior specification technique that allows to observe the database schema for inconsistencies and probable bottlenecks already in the phase of conceptual design. The conceptual schema is here used to (a) derive internal database representations, (b) compute on the internal representation behavior and performance properties of transactions, and (c) gain aspects for more advantageous conceptual schema design, in order to omit these problems. The target is to develope a conceptual database schema that derives an efficient database application, such that logical/physical tuning measures of after work phases can be farreaching avoided. A prototype conceptual database optimizer (CoDO) which has been developed in this research will be presented.Read the full paper here: https://link.springer.com/chapter/10.1007/BFb0019918
