SQL Server 2014 Database Design

This book is very helpful for learning how a SQL server database is structured and there are some good code samples that are good for creating basic queries and stored procedures. I thought that some of the topics in the book could have been ordered differently. Some of the later chapters should have been at the beginning of the book and some of the earlier chapters should have been toward the end. Overall, I think there are some great design tips in the book and I would definitely recommend it.

Poorly written, and a word for word copy of another book he sells. It was painful to try to read, no matter what chapter I tried.

Good book for teaching yourself computer programming. I took a ruby course and now I want to learn more so I am teaching myself as many computer languages as possible.

Good one.

Very informative; a good read

Good book, Design concept is properly given.

This author was evidently self-taught, and he had a bad teacher. The book is a disorganized compendium of notes and code examples that would be opaque to a beginner and found lacking by anyone who knows even a little about the subject. Few of the notes or examples have anything to do with database design, the titular subject of the book. It is painfully obvious that there was no editor, literary or technical, involved with producing this book. The book is padded with T-SQL code (much of it evidently generated using the GUI), result sets, and screenshots of SQL Server Management Studio. None of this material, which is the bulk of the book, is formatted well for an eBook, and most of the SQL statements would be useful only as examples of bad coding practice.The author is strangely obsessed by sorting, date formatting, the (pubs, Northwind, and AdventureWorks) sample databases, and integer identity columns as surrogate keys. The last is the only topic that fits the title, but it is never explained well, only advocated for, with none of the downsides (or even best practices) mentioned. While the sample databases are useful as sample schemas and data, they are certainly not paragons of database design, and the author never tells where one may get them. The author harps on normalization, which is a good thing, but his explanations are sketchy at best, with no examples given. One would be better served by just referring to Wikipedia.Although one could be cynical and posit that the author is deliberately obfuscating the basics of database design, hoping that a reader will be daunted by how difficult the topics seem from this book and hire an "expert" like the author (which he advocates several times), I instead think that the author has no aptitude for SQL and does not understand the subject himself. I did a quick search, and found support for my theory in several recent online forum posts ("answers") by the author.I write this review not to be malicious, but as a warning to those who choose a book (or an answer from an internet forum) only by its title or some faked bona fides written by the author. If I could give a negative five stars, I would, as this book will be detrimental to learning the subject; i.e., you will have to unlearn much of this material to progress.

It was free.

A terrible book. Terminology has been misused, some information is inaccurate. Do not buy.

I found the book lacking content