Database Design for Mere Mortals: : A Hands‐On Guide to Relational Database Design

Citation

Duffy, N. (1999), "Database Design for Mere Mortals: : A Hands‐On Guide to Relational Database Design", New Library World, Vol. 100 No. 3, pp. 147-147. https://doi.org/10.1108/nlw.1999.100.3.147.5

Having struggled with the topic of database design and development for two years on an Information and Library Management BA (Hons) course, the discovery of this book was akin to a drowning man coming across a life‐jacket. Current books on the subject tend to be written for people with a background in mathematics, computer science or those with experience in the computer industry. Alternatively, they are so simplistic as to be ineffective.

Michael J. Hernandez is the owner of DataTex Consulting Group in Seattle, Washington, and is an independent consultant and trainer, specializing in relational database management. Since 1988 Michael Hernandez has designed relational databases and created database applications for a wide variety of organizations and businesses, and he was a contributing editor for the database design chapter in Microsoft Access 2 Developer’s Handbook and the database design and macro chapters in Running Microsoft Access for Windows 95.

This book is aimed at all those who are interested in getting a database to work properly; the complete beginner will find that it explains the process of relational database design in a straightforward, commonsense manner, presented clearly with the minimum of technical jargon, while the experienced database developers and programmers will find that the new approach to the subject stimulates fresh ideas and methods. It focuses strictly on the logical design of the database, which the reader can then apply within any database software chosen. This fills a gap in the market, where so many books include chapters on implementing a database within specific database software, making it difficult for the reader to obtain useful information if they are unfamiliar with the particular software.

The book is divided into three parts. Part I explains in detail what a relational database is, what the design objectives should be and the importance of knowing and understanding the terminology used. Part II is devoted to the actual design process covering topics such as creating the data structures, determining and establishing table relationships, reviewing data integrity. Part III examines bad design and the rare occasions when you may be forced to bend or break the rules of database design. Simple examples are used throughout the book which help to focus the reader’s attention on specific concepts and techniques.

Appendices contain a list of recommended reading and sample database design diagrams, together with documentation forms which can be photocopied for use. The book has clear headings, is well spaced with easy to read print, and has a detailed alphabetical index at the back, e.g. Field Specifications offers sub‐sections on: anatomy of; general elements; logical elements; physical elements; specification information; case study in; defining, and reasons for importance. It is possible to read sections of particular interest independently, but the author strongly recommends reading the book in sequence, to keep everything in context.

The terminology used could cause confusion to the British reader initially, e.g. Chapter 9 covers Field Specifications, whereas Field Properties would be the more recognizable term in the UK, and a glossary would have been helpful. However, this is compensated by the author’s writing style, which achieves the unusual, in that he explains a complex subject in an uncomplicated manner.

Michael Hernandez says “you don’t have to be a rocket scientist to design a database” which, until this book became available, a great many of us thought we needed to be.