Enter your mobile number below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
Pro SQL Server 2008 Relational Database Design and Implementation (Expert's Voice in SQL Server) 2008th Edition
Use the Amazon App to scan ISBNs and compare prices.
Windows 10 For Dummies Video Training
Get up to speed with Windows 10 with this video training course from For Dummies. Learn more.
Customers Who Viewed This Item Also Viewed
Top Customer Reviews
How many times did you have to go back and change countless lines of code because your database was not normalized and it was not easy to add another payment type to the existing database?
This is where Pro SQL Server 2008 Relational Database Design and Implementation comes in; in the first couple of chapters you are taught how to design a database in a normal form. Most books that deal with database design are dry and boring; you need to read a chapter several times to digest the information leaving you with a headache. Not this book, Pro SQL Server 2008 Relational Database Design and Implementation makes this almost fun, the author goes through the phases of database design in a fun way which is understandable to the common man
After the design is done and you have your database you will be shown how you can protect the integrity of your data. Remember nothing in the database is as important as to make sure the data is correct, if you have bad data then you might as well have no data at all. This book will show you how to protect the integrity of your data by using constraints and triggers
There is a whole chapter of some good tips and tricks, patterns and query techniques. I think that you will find out you can solve a whole lot of business problems with a numbers table much faster than if you had to do it without
Security is a big topic these days, look on the internet, ever week you here horror stories how some data was stolen or otherwise compromised.Read more ›
In Chapter 1 Mr. Davidson does a good job summarizing the three, but he mysteriously adds a phase called "Implementation", which he attempts to use to mean the Physical Modeling, which is what EVERYONE else calls it. He then identifies a "Physical" phase as the tuning of an implemented model. Again, I cannot find ANY examples of this terminology being used this way. If he would have reversed these two names it would create much less confusion.
Meanwhile, he specifically identifies Conceptual Modeling "...consisting of a set of 'high-level' entities and the interactions between them" and Logical Modeling where "... you fully define the required set of entities, the relationships between them, the attributes of each entity, and the domains of these attributes...". This is consistent with the industry. Again, you identify detailed attributes at the Logical level.
But in Chapter 3, labeled "Conceptual Data Modeling", after going through a detailed example of requirements analysis, Mr. Davidson suddenly dives into attribute definition, all the way down to key structures! This is NOT Conceptual Modeling, and it conflicts with Chapter 1. The end of the chapter even has a section "Finishing the Conceptual Model." Chapter 4 discusses normalization, a step taken DURING Logical Modeling, but there is no mention of the progression from one phase to the next anywhere. By Chapter 5, the term Logical Model is suddenly used without warning.Read more ›
The title sounded very interesting to me & I was excited to learn a lot about SQL Server 2008. A large part of the book is about relational database design, which fair enough, hasn't really changed much and is mostly database independant. Hence the first part of the book has nothing much todo with SQL Server 2008.
For me, who's been working with database for a few years & I really wanted to improve my knowledge using this book. Whilst reading the book very carefully, what frustrated me the most, were the many many mistakes. Typos, content not making sense, incomplete updates from the previous edition, examples not working. Just so many mistakes on almost every page. If I received $10 for each mistake I found, I would make a small fortune.
A large part of the book is just full of references to other books to learn more about topics. There is truly very little SQL Server 2008 specific. Maybe nothing much changed or maybe the other was just too lazy to create new examples. Also, the sentences are often written in a way, which requires reading them 3 times before you understand what he means.
For such an expensive book & simple update from the last book --- very disappointing. Lots of room for improvement.
Most Recent Customer Reviews
I had not read a book covering database design since Uni, so this was a really good refresher. This was not a dull read - with a very good balance between technical detail and... Read morePublished on July 13, 2009 by MattF
I have some experience in database and web desinging as a hobby. As a non professional programmer, I can say this book was a real help guide for me in understanding relational... Read morePublished on June 25, 2009 by Mohamad Al-Karbi
This was the first book I got from SQL Server 2008. It's interesting how all the topics are presented because it takes you from very simple items like database fundamentals to way... Read morePublished on May 2, 2009 by Jose Rolando Guay Paz
In this age of TDD (Test Driven Design) I was interested to see what he would say about testing as it relates to the implementation of database designs. Read morePublished on April 13, 2009 by Craig Fisher
I don't know what Patric's problem is (and how could I? He wasn't specific at all). This book is simply great from start to finish. Read morePublished on January 10, 2009 by A. Bertrand