Buy Used
$4.00
FREE Shipping on orders over $35.
Condition: Used: Good
Comment: This book has already been loved by someone else. It MIGHT have some wear and tear on the edges, have some markings in it, or be an ex-library book. Over-all it is still a good book at a great price! (if it is supposed to contain a CD or access code, that may be missing)
Access codes and supplements are not guaranteed with used items.
Add to Cart
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Beginning Database Design (Wrox Beginning Guides) Paperback – December 5, 2005

ISBN-13: 978-0764574900 ISBN-10: 0764574906 Edition: 1st

Used
Price: $4.00
14 New from $18.49 25 Used from $0.01
Amazon Price New from Used from
Paperback
"Please retry"
$18.49 $0.01

Free%20Two-Day%20Shipping%20for%20College%20Students%20with%20Amazon%20Student



NO_CONTENT_IN_FEATURE

Save up to 90% on Textbooks
Rent textbooks, buy textbooks, or get up to 80% back when you sell us your books. Shop Now

Product Details

  • Series: Wrox Beginning Guides
  • Paperback: 504 pages
  • Publisher: Wrox; 1 edition (December 5, 2005)
  • Language: English
  • ISBN-10: 0764574906
  • ISBN-13: 978-0764574900
  • Product Dimensions: 1.1 x 7.4 x 9.2 inches
  • Shipping Weight: 1.6 pounds
  • Average Customer Review: 3.4 out of 5 stars  See all reviews (18 customer reviews)
  • Amazon Best Sellers Rank: #617,372 in Books (See Top 100 in Books)

Editorial Reviews

From the Back Cover

Database design involves how to best structure the tables and queries that are used with databases in order to provide optimum performance, storage, manageability, and flexibility. With relational databases, you can use those tables to organize your data and retrieve information from your database. This book provides you with an easy-to-understand explanation of designing and building relational database models to do just that.

The numerous step-by-step examples and a helpful case study simplify a potentially complex subject and present it to you in an organized, understandable manner. You'll find out why relational database models became necessary in the first place, and how the relational database model was devised. Ultimately, you'll discover how to make much better use of your database by applying what you've learned about building the database model.

What you will learn from this book

  • Basic concepts of relational database modeling
  • The components of a relational database model
  • Making normalization easier to use
  • Advanced relational database modeling
  • How to improve relational database model performance
  • Describing tables during using analysis (WHAT needs to be solved)
  • Refining tables and relationships using design (HOW to provide solutions)
  • How to read and write data with SQL
  • Create relational database models by applying business rules

Who this book is for

This book is for new database developers. No prior database or programming experience is required.

Wrox Beginning guides are crafted to make learning programming languages and technologies easier than you think, providing a structured, tutorial format that will guide you through all the techniques involved.

About the Author

Gavin Powell has a Bachelor of Science degree in Computer Science, with numerous professional accreditations and skills (including Microsoft Word, PowerPoint, Excel, Windows 2000, ERWin, and Paintshop, as well as Microsoft Access, Ingres, and Oracle relational databases, plus a multitude of application development languages). He has almost 20 years of contracting, consulting, and hands-on educating experience in both software development and database administration roles. He has worked with all sorts of tools and languages, on various platforms over the years. He has lived, studied, and worked on three different continents, and is now scratching out a living as a writer, musician, and family man. He can be contacted at oracledbaexpert@earthlink.net or info@oracledbaexpert.com. His Web site at http://www.oracledbaexpert.com offers information on database modeling, database software, and many development languages. Other titles by this author include Oracle Data Warehouse Tuning for 10g (Burlington, MA: Digital Press, 2005), Oracle 9i: SQL Exam Cram 2 (1Z0-007) (Indianapolis: Que, 2004), Oracle SQL: Jumpstart with Examples (Burlington, MA: Digital Press, 2004), Oracle Performance Tuning for 9i and 10g (Burlington, MA: Digital Press, 2003), ASP Scripting (Stephens City, VA: Virtual Training Company, 2005), Oracle Performance Tuning (Stephens City, VA: Virtual Training Company, 2004), Oracle Database Administration Fundamentals II (Stephens City, VA: Virtual Training Company, 2004), Oracle Database Administration Fundamentals I (Stephens City, VA: Virtual Training Company, 2003), and Introduction to Oracle 9i and Beyond: SQL & PL/SQL (Stephens City, VA: Virtual Training Company, 2003).

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

This is possibly the worst written technical book I've ever read.
R. Sandridge
I found several mistakes, and there is an awful lot of needless repetition.
A. Mandel
Good layout of chapters and lots of diagram with clear explanation.
Amish Shah

Most Helpful Customer Reviews

18 of 20 people found the following review helpful By R. Sandridge on January 30, 2006
Format: Paperback
This is possibly the worst written technical book I've ever read. I'd REALLY like my money back. Powell repeats some things over and over and over again. Sometimes, he re-phrases the same concept 3 or more times in the very same paragraph.

For example, I could not even guess how many times he explains that excessive normalization leads to poorer performance most of the time. I would guess he makes that point 30-50 times, and often 2-3 times on the same page. This is just one example, but the book is filled with fluff such as this.

There are also plenty of mistakes and awkwardly worded passages that make reading the book difficult. Many of the diagrams and examples could have been better chosen so as to reduce confusion.

So why did I give it 2 stars instead of 1? Well, there is *some* useful information in this book. I did learn some things from this book, but I'd like to stress that I don't think there is anything that I learned that I couldn't have learned from free sources on the internet. Take a look at [...] In addition to that link, do a search on "Entity Relationship Diagram", and you'll have learned 95% of what is in this book.

I almost feel bad making such a critical review, but on the other hand, I feel bad that I spent money on this book. I wish I had another title to recommend to you, but I've got to go looking myself for a replacement for this book.
3 Comments Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
9 of 11 people found the following review helpful By Mr. Panah Mosaferirad on December 17, 2005
Format: Paperback
This book is an excellent medium-level introduction to Database design. As a programmer, I was never really taught how to design efficient DBs or rather the art of doing it effectively. Believe it or not working with databases is more than just using SELECT or UPDATE commands. I believe DB Design is for rather medium to advanced users. So, others complains about the level of this book is unfair and irrelevant in my opinion. But you be the judge of that.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
4 of 4 people found the following review helpful By The Photographer on July 19, 2007
Format: Paperback Verified Purchase
In my experienced, the things that this author repeats over and over again are the most common mistakes in data modeling. I have seen over normalization in over 27 projects in my 15 years of experience. The author is simply trying to make sure that data modelers don't make these same mistakes again. For example, the most common performance problem with most relational databases is over normalization. That means that an application developer may have to do dozens of joins to produce the resulting data. I have seen people use as many as 22 joins, group by, and all kinds of business logic in SQL in order to produce one short sentence of data. That also means that some of the business logic will be shifted to the third or data tier and not kept in the correct tier, middle tier, application tier, etc. This ruins the performance paid for by developing the multi-tier system in the first place.

That is fine if the system will be used by one user, but multiply that by 10 million unique users in 12 hours on an enterprise database, and one has a big problem.

One must always consider the purpose of the model, and how the data will be taken out of the model as well as data integrity, security and normalization.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
5 of 6 people found the following review helpful By A. Mandel on February 25, 2009
Format: Paperback
I'm a fairly technical person, but my knowledge of databases was superficial, so I decided to read this book. It is billed as suitable for the novice, and therefore should take things slowly and methodically.

It feels disjointed and poorly structured. The author seems to jump from one topic to the next. But probably the most significant problem is that the author uses terms and concepts before defining or describing them. I can only imagine how confused a true novice might be when reading some of this.

Examples:

He talks about Online Transaction Processing and Data Warehousing without really defining them or giving examples that would help the reader understand what they're used for.

On page 10, there is a figure purportedly showing what a relational database model looks like. However, it uses symbols and lines that he does not explain till later in the book. Without explaining the symbols, what good is the diagram?

Many places, he talks about normalization before explaining what it is. In one spot where he starts to explain normalization, he writes, "Normal Forms beyond 3rd Normal Form are often ignored and sometimes even 3rd Normal Form itself is discounted." He does not explain what a Normal Form is.It's just text that will have no meaning at all to the reader.

He talks about tables and columns before adequately explaining what they are.

In Chapter 3, he covers simple datatypes. First, he explains what a fixed length string is. But in his accompanying diagram, he uses SQL constructs to explain it.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
8 of 11 people found the following review helpful By derazz on February 3, 2006
Format: Paperback
That which i found very useful about this book, was the ability it bestows on one to take/translate an abstract, ordinary typical user sentence like: "we don't want customer orders to be bookable to our website and thereby representing for us a negative quantity value against our stock inventory,if the quantity we have left in stock for the item is actually zero"

and translate it straight into the SQL implementation equivalent. for example: using a table definition to define restrictions to a single quantity-in-stock column , as well as a table check-constraint requiring (quantity-required to be less than , or be the same as, the amount of the quantity-in-stock), one possible SQL implementation equivalent of the user sentence could be shown in T-SQL as:

CREATE TABLE ProductOrderLine

(ProductLineKey....BigInt....,

OrderMatchKey.....BigInt....,

ProductOrdered....Char(6)..,

QuantityInStock....BigInt....,

...CONSTRAINT NonNegativeStockValue CHECK (QuantityInStock >= 0)

QtyRequired.......BigInt......,

...CONSTRAINT CK_QuantityOrdered CHECK (QtyRequired <= QuantityInStock))

In short, Beginning Database Design by Wrox, gives one a useful,solid level of clarity/handle in grasping this direct relationship between your understanding of the business rules and user requirements for the database system and the direct SQL translation of this into SQL code implemention.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Customer Images

Most Recent Customer Reviews

Search

What Other Items Do Customers Buy After Viewing This Item?