scientific article; zbMATH DE number 2173817
The reviewed book reflects recent changes in modern database management systems. During their many years of consultancy in the information industry, the authors experienced the impact of new features which have caused a movement away from truly normalized database design. In the introduction, the authors describe roughly the matter of their book: ``However, for a DBMS to efficiently support the storage and retrieval of company data, the schema design must be implemented with an understanding of the structure of the data and how it will be accessed. The logical design allows one to analyze the data itself. Once one has the logical design, one needs to move to the physical design. The physical design is based on the capabilities of the DBMS selected to host the data. The authors start with traditional relational design principles. They follow up with design for specific purposes such as object-oriented, on-line transaction processing (OLTP), and data warehouses. This shifting away from relational design forced the authors to move away from purely logical design into some of the physical design. This is caused due to the way in which ``many of the features of modern databases are implemented. The authors attempt to make the examples vendor-neutral. However, sometimes vendor-related examples are used when a certain implementation underlines the discussed concept with extra clarity. The chapters of the book: Introduction to Logical Database Design, System Design and Implementation, Converting the Logical Data Model, Formal Data Normalization, Data Denormalization, Object-Oriented Design, Object-Relational design, Designing Replicated Databases, Design of the OLTP Database, Design of Data Warehouses and Decision Support System Databases. The reader does not need a theoretic background of database design. The examples illustrate the writing clearly. The book is recommended to practitioners and project managers etc. who want to get an overview on developments in database design from the viewpoint of large, company-wide databases (for example supported by Oracle DBMS).
- Design of logical database structure for data handling systems
- Logical data modeling. What it is and how to do it.
- Database modeling and design: logical design.
- Automated physical database design and tuning.
- scientific article; zbMATH DE number 108406 (Why is no real title available?)
- scientific article; zbMATH DE number 2210707 (Why is no real title available?)
This page was built for publication:
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q4680562)