Download Ebook Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition)
One that makes this publication is strongly checked out by quantities individuals is that it gives a different way to utter the meaning of this book for the visitor. Easy to review and also easy to understand become one part personalities that people will consider in choosing a book. So, it is extremely appropriate to take into consideration Database Design For Mere Mortals: A Hands-On Guide To Relational Database Design (3rd Edition) as your analysis product.
Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition)
Download Ebook Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition)
Waiting to an enhanced thoughts and minds are a must. It is not only done by the people that have huge tasks. That's additionally not only performed by the students or income earners in fixing their responsibilities issues. Every person has exact same possibility to look for and also look forward for their life. Improving the minds and also thoughts for better lifestyle is a must. When you have decided the methods of just how you get the issues and take the addressing, you should need reflections and also ideas.
When you need a book to review currently, Database Design For Mere Mortals: A Hands-On Guide To Relational Database Design (3rd Edition) can be a choice because this is one of the upgraded publications to read. It makes certain that when you have brand-new thing to think about, you require inspirations to address t. and when you have time to read, guides turn into one remedy to take. Also this publication is thought about as brand-new book, many individuals put their trust funds on it. It will certainly recognize you to be one of them that are falling in love to read.
Well, even this book is provided in different with the printed publication; it will not be big issue. You recognize why this web site has several fans? Well, all provided books have the soft data. It is delivered based upon the title. When you take a look at the web site in this page, finding the link to get this Database Design For Mere Mortals: A Hands-On Guide To Relational Database Design (3rd Edition) is simple. Just follow it as well as discover the book.
After obtaining the soft data, you could conveniently produce brand-new motivations in your mind. It is difficult to obtain guide in your city, possibly furthermore by going to the shop. Seeing the shop will not also provide warranty to obtain the book? So, why do not you take Database Design For Mere Mortals: A Hands-On Guide To Relational Database Design (3rd Edition) in this website? Even that's only the soft documents; you could really feel that the book will certainly be so helpful for you and life around.
About the Author
Michael J. Hernandez, a relational database developer with more than twenty years of experience, was a program manager and product manager for Microsoft’s Visual Studio group. He has been a premier instructor with organizations such as AppDev Training Co., Focal Point, Inc., and Deep Training, and was a top-rated speaker at technical conferences across the United States, Europe, and South America. With John L. Viescas, he coauthored SQL Queries for Mere Mortals®, Second Edition (Addison-Wesley, 2008).
Read more
Product details
Series: For Mere Mortals
Paperback: 672 pages
Publisher: Addison-Wesley Professional; 3 edition (February 24, 2013)
Language: English
ISBN-10: 9780321884497
ISBN-13: 978-0321884497
ASIN: 0321884493
Product Dimensions:
7.4 x 1.6 x 9 inches
Shipping Weight: 2.4 pounds (View shipping rates and policies)
Average Customer Review:
4.1 out of 5 stars
165 customer reviews
Amazon Best Sellers Rank:
#57,215 in Books (See Top 100 in Books)
First off, this book is well-written. Mr. Hernandez does a good job of explaining the "why" behind his explanations. He also provides tips that just seem to make sense. He advises that a table have a name that is plural, because each record is one "instance" of the data related to the table. As an example, a table called CarColors would have several rows, each containing one car color.My only real criticisms are:1. That he did not go enough into effectively indexing, applying primary/foreign keys, and applying constraints.2. There was not enough discussion of the various "normalized" forms, when they should be used, and so forth. This is covered in a "flyover" manner that makes sense, but perhaps a more "in-depth" discussion of normalized forms is beyond the scope of the book.I felt like I knew most of the information, but I didn't feel this book was a waste of money, as many of his "common sense" approaches I will utilize in my own DB designs in the future.
Thus far I see no difference between this and the 2nd Edition, so if you already have that version you don't need this one. That being said, it doesn't make this edition any less deserving of five stars. My professor, a full time Software Architect, recommended this book to me four years ago. Now, as a successful Software Developer, I'm recommending it as well. Based on my experience, this book covers everything one needs to know about database design.
I found this book very thorough at an introductory level and well written. I think someone with no database experience at all could read this and help with database design. The only criticism I have is the verbosity. Some things are repeated or can be assumed.This book does not get into normalization or any details, which I liked.
I like that book. It was easy to read, unfortunately there is to much of copy paste. I would rate it 5 stars if book took just 300 pages, seriously there is not much in order to make 600 pages. But approach brought by author is interesting, anyway I would like to ask the question. How good does this approach fit at 2018 with agile, scrum? I am not sure that I'll get back to read this book one more time, which is really important sign for me, maybe because it is easy book. What I don't like very much, author mention that competitor authors don't know something, well...
This book provides the basic concepts for good relational database design. It is structured in a very easy to read format. It clearly walks you thought design objectives and defining tables, keys, fields, table relationships, as well as business rules. Chapter 14 is an interesting chapter titled "Bad Design - What Not to Do".
I wish more technical primers were written like this. All new terms are clearly explained.
No, this is not the book for you if you have extensive experience in software design and have already absorbed the basic concepts of database design by osmosis.This is a book for "mere mortals," just like it says. I'm a reasonably smart, reasonably well-educated person who had some computer experience, but didn't even really know what a relational database was. Through circumstances too odd to mention, I was given primary responsibility for designing a commercial web application.I read this book cover to cover, and designed the database that became the core of the product. The product actually works, and seems to be selling. Later in the development cycle, I worked with a brilliant MIT-trained software engineer, and he found my basic db design just ducky.I definitely owe Mr. Hernandez a beer. Figured writing this review was a reasonable substitute.
Michael Hernandez does a great job of explaining how the relational model works, and how a database should be designed from start to finish. Most of us will probably not follow his advice, though.If you do decide to follow his advice, then be prepared for a very lengthy trip when designing your DBs. I tried on my first DB and found that the company I was designing the DB for started to get slightly irritated. This is because in this book Michael suggests you have a full blown manager and or user meeting with virtually every single change you make (also meetings for requirements, ideas, characteristic identification, user input meetings, manager meetings... oh look, a change happened, now we have to go through all of the same meetings again... and again... and... >yawn<... every other page in this book suggests another meeting). I must have had 25-30 meetings total, which just isn't necessary. Also, there is all sorts of spec sheets you should fill out for every single aspect of the database. I would probably just use a modeling tool (such as Visio) instead of going through this daunting task (I would have had to fill out over 300 spec sheets just for the fields!... it was a big DB)Although his way of designing is probably the way you should really go, I found that designing a sound database doesn't require quite so much work. You can do most of the design process if you have a good modeling tool, which is what I ended up doing and my DB turned out quite well (you still should conduct meetings, but not for every single aspect of the database... your clients will begin to think you have no idea what you're doing). However, this book pounds the relational design in your head so much, that you can't help but get over the tough learning curve of how a relational database really should be designed.
Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition) PDF
Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition) EPub
Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition) Doc
Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition) iBooks
Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition) rtf
Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition) Mobipocket
Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition) Kindle
0 komentar:
Posting Komentar