1 of 1 people found the following review helpful
full of typo's, bad enuff, but NO errata page is UNFORGIVABLE,
Verified Purchase(What is this?)
This review is from: Beginning SQL Server 2008 for Developers: From Novice to Professional (Expert's Voice in SQL Server) (Paperback)
The book looks like it was rushed out the door as the earlier chapters in particualar are full of typo's, and sentences/passages that just don't make sense, or are just plain contradictory e.g p10:
"Client Tools: Some of these tools sit on the client machine and provide the graphical intreface to SQL Server, while others sit on the client and work with SQL Server."
Now, after thinking for a minute or two it became obvious to me as someone with 15years general computing experience that the author meant to write "server" instead of the second instance of "client". But a) I don't want to have to do this thinking to make up for the editor's laziness and b) A beginner here wouldn't be able to spot the mistake and would be confused, or worse, go away with duff information!
Here's another one, p17:
"A service can be set to start automatically before any user has even logged on; all other programs require a user to be logged in to Windows in order for the services to start."
This is just plain confusing... Even I struggle with what this means, and I used to program services for a living! I think if you replace the 3rd last word "services" with "these programs", it makes sense. But maybe he meant non-auto startup services can be started manually when someone logs in?
I'd rather be scratching my head trying to understand SQL Server 2008, not the author's writing style.
I went onto the book's site on Apress to check the errata to get these and other issues cleared up, or log them if they weren't there. NO FACILITY for submitting errata !! There is a form there, but nothing happens if you fill it in (more time wasted !!!).
Had there been just the errors, I would have given 3 stars, but the LACK of ERRATA page, in a tech book riddled with errata is just plain UNFOGIVABLE. Avoid this book!
ASIDE: This is not the first Apress book without an errata mechanism. Readers NEED the errata pages, and I encourage all reviewers to give books that have errors, but no errata page, an automatic 1star, until the publishers wake up and start putting some effort into errata and corrections.
I will continue to post errata here. Hopefully Apress will transfer them onto the proper place, and I can them remove them. Until then, 1star review.
Who is with me on this?
Sort: Oldest first | Newest first
Showing 1-10 of 29 posts in this discussion
Initial post: 21 Jan 2010 20:57:50 GMT
ERRATUM: p104, "Trying It Out", bullet #3
"We have seen this screen a couple of times already, so there is no need to explain it again."
No! we haven't encountered this "screen" (dialog actually) in the book yet, so pls explain it here.
Posted on 22 Jan 2010 07:01:48 GMT
ERRATUM: p116, bullet point #8:
"highlight the policy, right-click, and select Test Policy from the pop-up menu."
My pop-up menu is the same as the one shown in the figure, except that "Test Policy" is replaced by "Evaluate".
Posted on 22 Jan 2010 07:02:42 GMT
[Deleted by the author on 22 Jan 2010 07:02:50 GMT]
Posted on 22 Jan 2010 07:03:57 GMT
ERRATUM: p117, all of it
The UI for this feature is different from that displayed in the figures.
Posted on 22 Jan 2010 07:20:21 GMT
ERRATUM: p130, figure 5-5
IN the figure, Allow Nulls is set to "Yes". However we have just unset "Allow Nulls" by unchecking the box above, so this is inaccurate.
Posted on 23 Jan 2010 17:25:21 GMT
"Creating a Relationship"
Doesn't make sense or seem like good practice to say something like: "Keep in mind that although a customer may have several customer records-one for each product he or she has bought....". Either the entity-relationship analysis is a bit screwy or there are typos here (i.e. "customers table should really be customerProducts table).
Posted on 23 Jan 2010 20:28:37 GMT
The INSERT statement syntax at the top of the page:
There should not be curly brackets around the column_names. Curly brackets indicate a choice of alternatives, which is not appropriate in this line.
Posted on 23 Jan 2010 21:13:35 GMT
Robin Dewson says:
Thanks for the review and the rating. I do appreciate the honesty and apologise for the problems it may have caused you. I dont feel that the book is "riddled" with errors, but I agree that you have found some problems, some are confusing
Concerning the erratum I am not in control of this process at Apress, and have even notified Apress of errors that have slipped through. I will put up a page on my own site to cater for your and other points. I hope this helps you and other readers.
Thank you for posting what you have found and if you wish to contact me directly then please do
Posted on 23 Jan 2010 22:34:54 GMT
Last edited by the author on 23 Jan 2010 22:35:16 GMT
ERRATUM: p254, step #2 in Try it Out
Replace "Open Table" with "Edit Top 200 Rows". I think "Open Table" is a relic from an older version, I know its there in SQL2000 'cos I was using it on Friday!
Posted on 24 Jan 2010 00:04:08 GMT
ERRATUM: p258, Column Constraints
The first line of the code example looks wacko! My installation of SQL Server 2008 actually spat this out instead:
ALTER TABLE [CustomerDetails].[Customers]
ADD CONSTRAINT [DF_Customers_DateAdded]
DEFAULT (getdate()) FOR [DateAdded]