<< 1 >>
Rating: 
Summary: Subtitle: If you learn 24 / 4 (hour) per day
Review: I have a mixed feeling about this book. It does cover the basic operations of getting SQL server up and running. However, it's written in a dry style that's enough to make you fall asleep at times (most of my C++ books don't). Regardless, after reading this book in a few days, you should be able to set up a fully functional SQL server. The author does not cover some essential elements such as good datebase fundamental knowledge (i.e. normalization). It doesn't go over much of the TSQL syntax (you just have to learn by trial and error). The goal of the "learn xyz in 24 hours" book series is distorted. Especially on a large topic such as SQL database software. The problem is that while you can technically learn the material in 24 hours but the way they organized the material is gear toward a short 1 day course. Unfortunately, since the reader would have to realistically spend a few days go through the book and practice anyway, why leave out all the necessary details? It's one of those books you buy and read once and never use again because of its depth (or lack of). If you are new to database design - this is NOT the book to buy. However, if you have some fundamental knowledge of good database design and some experience with database like Access, C++, VB, this book does it job.
Rating: 
Summary: The book is good...and bad, really bad.
Review: My favorite error is, referring to IF...ELSE statements on p329, "If you do not include an ELSE statement, SQL Server will simply skip the code after the ELSE statement and continue on". Hmmm?, I thought the ELSE statement wasn't included? Of course I also liked the authors fine use of COPY/PASTE; the 1 page+ long list of Stored Procedure Options/Description which are duplicated exactly within the same chapter [on Stored Procedures] a few pages apart (p311 & p319). Once for creating a new SP, and again for modifying one. THE TEXT IS AN EXACT COPY. Geeze, what a waste of paper! Next time try "See figure 123". But once I got beyond the poor logic, poor editing, poor proof reading, and typos, to the authors credit, I did find the book useful. It's certainly for beginners, and as such it reads at that level. Very easy. I also found the examples to be very useful. Something IMHO I find lacking in other "beginner" books. Would I recommend it? Well, I'd have a hard time doing so considering all the blunders. Would I recommend the Second Edition (if it ever came out)? Yes. I think it would be very helpful. Tim <><
Rating:
Summary: The book is good...and bad, really bad.
Review: My favorite error is, referring to IF...ELSE statements on p329, "If you do not include an ELSE statement, SQL Server will simply skip the code after the ELSE statement and continue on". Hmmm?, I thought the ELSE statement wasn't included? Of course I also liked the authors fine use of COPY/PASTE; the 1 page+ long list of Stored Procedure Options/Description which are duplicated exactly within the same chapter [on Stored Procedures] a few pages apart (p311 & p319). Once for creating a new SP, and again for modifying one. THE TEXT IS AN EXACT COPY. Geeze, what a waste of paper! Next time try "See figure 123". But once I got beyond the poor logic, poor editing, poor proof reading, and typos, to the authors credit, I did find the book useful. It's certainly for beginners, and as such it reads at that level. Very easy. I also found the examples to be very useful. Something IMHO I find lacking in other "beginner" books. Would I recommend it? Well, I'd have a hard time doing so considering all the blunders. Would I recommend the Second Edition (if it ever came out)? Yes. I think it would be very helpful. Tim <><
Rating: 
Summary: Basically Good
Review: This book is a good overview for a beginner. Nothing too fancy. There are quite a few editing mistakes, though.
Rating:
Summary: Basically Good
Review: This book is a good overview for a beginner. Nothing too fancy. There are quite a few editing mistakes, though.
<< 1 >>
| 
