Software Books

This book is a must have to a DBA. It contains all the little gotchas in managing SQL Server. All the items that we come across while searching for something that I think"Man I gotta remember that". 99% of them are in this book, so I don't have to print them out and maintain a seperate library.

Not a book to buy if you are looking something to read to learn SQL Server. This is a reference for someone who already is using it extensivly.

Ross

Overall, this is an excellent book that covers a wide variety of topics useful to any SQL Server 2000 DBA. At this time, though Apress hasn't posted the Table of Contents on Amazon.com, the Table of Contents is posted at the Apress web site.

I took away one star for the CD. It is extremely handy to have a copy of the book on the CD in PDF format. However, rather than having a single PDF file with a Table of Contents linking to each chapter and topic, each chapter is contained in a separate PDF file on the CD. Unless you know which chapter you want to reference, it is tedious to look in separate files for the Table of Contents or the Index, then try to guess in which file the item you are looking for can be found.

A less significant complaint is that the CD holder is found about three-quarters of the way through the book, rather than at the end of the book, which makes it more difficult to quickly flip through the book.

Other than these minor complaints, it is an excellent book.

This is an easy to use reference book. It has a useful index and directions are written in a step by step format.

This book has 100s of relevant and useful "How Tos". Very useful.

Not a tutorial, but a practical working guide to administering SQL Server 2000. Lots of "How to" items covered.

You don't need to read the entire book in order to benefit from it. Specific topics are covered using Checklists to make sure you don't miss anything important. Highly recommended!

This book is one of the best programming language books I've read, along with "Oh! Pascal!" by Cooper and Clancy. It's use of humor and simple, straightforward examples, grab your attention right away and keep it through the entire book. It's hard to believe a programming book can be hard to put down, but this one was.

It also explains complex concepts in simple, elegant ways, just like good programs should be written.

I would recommend it to anyone learning FORTH, and I would recommend sections of it for people trying to understand specific concepts in any language. For example, the explanation of stacks was excellent!

I bought my own used copy of this book, but it is available in its entirety online, so it is unlikely to ever be reprinted.

Somebody REPRINT THIS BOOK!

"Starting Forth" is the only Forth book I own. After reading it, I was able to implement a Forth runtime system, compiler, and interpreter, from scratch, in 8086 assembly - the results can be found at home.earthlink.net/~jknapka/jkf.html . I credit this mainly to Leo Brodie's skill as an expository writer. The book is a gem; if someone were to reprint it, I for one would buy several copies, just in case.

The reason no one will reprint "Starting Forth" is that Forth is not sufficiently trendy. If we rename the language "JavaForth", we'll be drowning in reprints...

Sigh.

This book is a very clear introduction to programming and the stack. The cartoons are very entertaining and descriptive, and the book would make light reading even for beginning programmers. Those who program, but not yet in Forth, will also be happy with the quick introduction.

Why on earth is this fabulous book out of print?

A wonderful book. I bought mine in 1980, and a week later I had an old Northstar Z-80 computer running real-time behavioral experiments in FORTH at (so it seemed) blinding speed.

We need this book!

I bought "Succeeding with Use Cases" primarily for Part 3 on model-based specification. The book gives a "Blue Collar" approach for specifying operations in terms of change of state. The approach is highly pragmatic and aids writing precise, testable specifications. The author clearly explains what to do. I highly recommend this book.

Example after example; model after model! After reading this book, I was ready to begin implementation! Chapter 3, Operational Profiles, will convince and evangelize engineering and management. The degree of detail is perfect for the professional. Great Work!

I was really happy to see Richard's new book. I have always thought that if you are going to go to the effort of writing good use cases, then you should make use of that information as much as possible in the project. This book has a prominant place on my professional bookshelf, and I refer to it often.

Richard Denney gives some great information on using your project use cases in project management, quality control, and reliability. He has a wealth of experience that he shares throughout the book. His book is well written and easy to understand. I am not aware of any other book that covers this information in the context of a software project.

Once you are comfortable with writing use cases (and of course I must recommend my own book Applying Use Cases: A Practical Guide for that purpose), then definitely start exploring what you can do with the use cases once they are written by getting a copy of Richard Denney's book, Succeeding With Use Cases: Working Smart to Deliver Quality.

This book is about uses of use cases in software engineering. The focus is on doing and managing projects.
Topics are among others selection of standard products, management of project portfolios, or grounding projects in business goals. The last topic is an application of use cases to QFD, a process originally from the automobile industry. Other topics are reliability engineering, modelling and project management (this list is not complete).
All the topics of the book have use cases as a common factor. It is not an introduction into use cases. The application of use cases in this book goes further than what is described in the Rational Unified Process for example. Therefore other books are better in introducing the topic of use cases.
Demo excel sheets are available from the author. The examples are worked out excellently and instructive. The book focuses on the practicalites of software engineering and addresses primarily project leads, designer, architects and testers. Most of the material was new to new, although I have been using use cases for years. It will have the most value for organizations already modelling their software. In my opinion extreme programmers will not find it as useful.

I'm a software engineer, specializing in requirements and software quality. I've known about QFD and the House of Quality for over a decade, and I've been using Use Case methodology for years. This is the first (and perhaps the only) book which combines the two methodologies and explains in a straightforward yet sufficiently detailed way how to use these methodologies. If you are struggling with many requests from multiple customers and are trying to identify what is really important, you should read this book. In particular, if you want to satisfy the customers who drive your business, i.e., generate revenue, you need to read this book. This is a low-tech approach; all you need is a spreadsheet. Understanding Use Cases, QFD, or House of Quality is not a prerequisite. Even if you are already familiar with these methodologies, I think you will still learn a lot from this excellent book.

I loved this book. It covers the history of Open Source and explain WHY people do open source and HOW they make it happen!

The Success of Open Source in a not a just wistful paean to Linux as the title would suggest. Rather, it is two books in one.

The first book is one of the very best recapitulations of the open source movement and all of its predecessors. The second book is about how something that just seemingly shouldn't work, works so well, and how those principles behind its working extend to more than just the open source movement.

The author, a university professor, draws liberally from the traditions of historians, economists, sociologists, and psychologists to paint a compelling picture of why the forces behind open source are not going to go away any time soon. Read in best companion with The Cathedral and the Bazaar, which IS a bit of a wistful paean to Linux, it illuminates its subject wonderfully.

Steven's book brings a rich articulation of the social practices innovations unleashed by the Open Source collective: a new understanding of private property that better fit the tech forces and the challenges of the present. His book it is not a model; it is not the list of the 10 reasons why...; it is not the defense of an emerging theory; but an historical account in which anecdotes, facts, historical moment, tentative hypothesis, set the background to allows the reader to reshape her/his own questions. The book gave me a perspective I have been testing with IT architects, programmers, software designers...I feel myself much more prepare to engage in conversations about the future in a meaningful and effective way. Thanks to the author!

For the serious reader (and who indeed thinks open source is hilarious?), Weber provides a detailed history of how this idea developed. He traces it from the advent of unix in the 1970s, and the generous (ie. low fees) licensing terms by ATT. Which led to the BSD Unix that flourished in the 80s. Also during this time, GNU took off.

But the bulk of the book deals with the 90s onwards. Especially as linux grew from Torvalds' seminal contribution. Its intellectual roots in unix and GNU are studied. We also see the rise of the Free Software Foundation and Apache, as articulate enablers and promoters of open source. All of which was aided by the invention and meteoric growth of the Web. This played a vital role in enabling a global audience of programmers to hear of and contribute their efforts.

I'm a commercial software developer, and found the author's history of the UNIX culture and the story of its evolution into what we now call Open Source to be fascinating. That alone made it a good read for me. Add in the thought provoking analysis of the "whys" (the real point of this book), and it's a killer combo.

Warning: the book is *full* of sentences like "Pluralism at many different levels is being enabled by communications technologies and by experimentation with property; together, these are reducing the marginal cost of adding voices toward an asymptote of zero." Despite that, I've been able to read it at the pace of a thriller, not a textbook.

I have never seen such a complete book in Data base. I am hoping to find a good book related to SQL Server like this book.(Anyone can help me?)

Very nicely written. Lot of care has been taken to make things as clear as possible.

The book provides an excellent understanding of Access97. You read and it seems you haven't learned much, yet you can do alot. The split up on each day makes the reading process easy and on a schedule. The book also covers the basics which form the complete advanced sections of Access97. Finally, the book covers the program well and allows the reader to know what has to be done and then has the option to use help to figure how to do it.

If you really are new to Access, look no further for a book to aid you.. Paul Cassel teaches the way you want to be taught, by example. The best $23.00 I could have spent to learn something.

If you want to learn how to use Access 97 this is a great way to begin. You can work your way through the book at your own pace. Each "day" teaches a new concept. When you are done, you will have a good basic understanding of how to use Access.

This book is about web testing in general, not just performance testing, and is a must have for the professional testing engineer. Chapters 7 and 8, on performance and scalability give a very good introduction to the subject, and include a great sample performance testing plan.

Michael Czeiszperger
Web Performance, Inc. Stress Testing Software
http://www.webperformanceinc.com

When industry leaders such as Cem Kaner and Bret Pettichord extol the virtues of this book you can be assured that it is great - everything they and other reviewers have said is on target. Moreover, you'd be hard-pressed to walk into the testing area in any company and not see a copy of this book on someone's desk.

That said, instead of this book you should get the second edition, which is a major rewrite, and also expanded in scope to include testing mobile systems. This edition is titled, "Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems" ISBN 0471201006, and is everything others have said about this first edition - and more!

Even with a better second edition, this book deserves the five stars I gave it because of the influence it has had on the testing profession. Moreoever, this first edition is not out-of-date, and is still a great book if you don't need information about testing mobile web systems at this time (although it's a safe bet you will in the future).

Grey box testing is based on a general understanding of a system's architecture and components. This understanding drives test strategy and identifies opportunities to test components in isolation.

The shade of grey can vary from white box testing (full review of source code) to black box testing (no review of source code). You choose what level of information to gather depending on your budget, capabilities and judgment.

This book provides the first detailed approach to grey box testing, focussing on web-based application architectures. These architectures are based on a heavy use of components: application servers, web servers, load balancers, databases and the like. This book describes these components, suggests how they can fail and what you can do to anticipate, trigger, or detect such failures.

This approach is supported by the author's extensive experience testing web-based (and other) applications as president of a software testing company. It is augmented by plenty of good advice on how to communicate test results clearly.

I have been in web testing for 3.5 years and this was the first book I found on the subject. My only complaint is that it took so long to come out, but I won't hold that against Nguyen or Wiley. It is a superb introduction to the complexities of web testing, which despite the protests of standalone application testers, is much more difficult and technical than traditional application testing. Not only does the tester need to know the basics of application testing, he or she has to know about the complex technology behind the site or application, and Nguyen's book is unbeatable. I've recommended that everyone on my team read it, since they are all new to the art of web testing. I read it cover to cover and it didn't really cover anything I had not learned in 3.5 years of experience, but had it been published when I started, I would have been able to ramp up so much faster. I also recommend that application developers read it in order to understand the role of a tester and to develop professional respect for a much-maligned profession.

This is good book. If you test web apps, you should buy it.

Hung Nguyen and I are co-authors of another book and good friends. I am not an unbiased reviewer. On the other hand, I wouldn't write this review if I didn't believe every word of it.

Hung's book breaks new ground. It will be useful today, and I believe it will have lasting value and influence.

Once you get beyond the superficial (not unimportant, but much less difficult) issues of usability testing that dominate so many discussions of web testing, you run into the really tough problems of web application testing. Hung Nguyen's book is about those harder problems.

The web-based application runs on a wider range of platforms than any other type of program in history. It doesn't even have control over its presentation layer (the user supplies the browser and the multimedia plugins, and these applications might change any time). What will the application look like on the changed browser? The application probably also relies on third party databases (which can change any time), third party network connections (which can change any time), third party security systems and other access control (which can change any time), etc., etc. Almost anything in this system can change any time. How do you deal with a system that has so many unknowns?

Hung's view is that web application testers must learn more about the technical details of the systems and understand how external variables can interact (and fail) with the application under test.

To help testers learn about the interaction (and testing) of applications with other system components, he wrote the field's first book on grey box testing.

This book has substantial value for what it teaches us about testing on the web. Beyond that, it teaches about thinking clearly and thoroughly when your application interacts in complex ways with other systems. I think his approach will have lasting value and lasting influence long after many of the detailed issues that he describes have been resolved and replaced with new ones.

Along with the original approach, Hung gives a powerful real-world example. He is the president of a company that publishes a web-based bug tracking system. To illustrate the types of tests that you can run and the types of bugs you can find, he opened his records and described real tests, real bugs, and real testing problems. It's a rare treat to see a discussion of testing experience by someone who knows testing, who also intimately knows the software under test, and who isn't constrained in what he can say by a nondisclosure contract.

...with regards to COM+ before I read this book. A definite eye-opener! Very well written, explains in a concise manner both the big picture but most importantly IMHO the little details, those little holes that prevent you from fully understanding what is going on, what is happening, when, where and why.
I had considerable plain-vanilla-COM experience when I read it, but I believe it can be of immense help even to COM novices (I wish I had read that amazing explanation of COM apartments as a thread affinity issue a couple of years back).
This book is so good, I would gladly buy a second copy!!!
Thank you, thank you, thank you Tim!!!

I'm a professional software engineer with twenty years experience, so I've read my share of computer books and dipped into hundreds more.

This is quite simply one of the best computer books I've ever encountered. A classic.

So many computer books are just rehashes of vendor documentation, vague or misleading or wrong in all the same places the vendor documentation is. This book is different. The author clearly has tested every assertion with his own "spelunking" code. He explores every nook and cranny of COM+, and every sentence is carefully considered, clearly stated, and as far as I can tell, absolutely accurate. There's no "hand-waving", no BS, it's just absolutely solid. Crystal clear, razor sharp.

It's a shame, really, that the title is "Transactional" COM+. I had the book for quite a while before I got around to reading it, because the title misled me into thinking that if I wasn't using transactions then it didn't apply to me. Wrong! This book covers COM+ generally, not just transactions, with particular emphasis on the elements of COM+ that are most likely to affect scalability of middle tier applications. Want to know what threading models to use in components called from ASPs? Want to really understand why? This is where to find out.

It's a serious work and really deserves to be studied with some care, but whatever effort you put into studying it will be amply rewarded.

If only all computer book authors were as smart, as conscientious, and as intellectually honest as Tim Ewald. Bravo!

...What the hell is the IMarshal3 interface?

The previous reviewer seems to be disappointed that most of the book's sample code is written in C++. Alas, at this time (and until the moment, perhaps in the second release of .NET, when the COM+ component services are implemented in managed code) a significant part of the COM+ infrastructure is simply inaccesible from Visual Basic.

As the title and the preface state, the book's focus is on transactions in the COM+ environment of Windows 2000. Perhaps a list of "requirements", and don't take these too serious, will decrease the number of disappointed readers:

The reader should:

-know the basics of COM

-be comfortable reading C++ code (Although VB or JScript is used now and then)

-know, or read up on, the ATL util classes (CComPtr, CComBSTR)

-same thing for OLE DB (& the ATL consumer wrappers)

What the book does not cover (and again, this is stated in the preface):

-LCE (COM+ Events) and QC

-CRMs

-Security topics

The structure loosly resembles "Essential COM". (that's a compliment :-) )

In my opinion the book delivers on it's promises.

One of the great book. Every COM+ developers should keep a copy

Clear, concise and honest this book is for the advanced programmer/architect. It shows all the inners of COM+ and everything is based on serious theoretical background that too many of the developers today are missing.
Excellent.

It is funny how I was glancing at the books and this book Voice XML caught my attention. I was looking for a book like this. This is a great resource for Voice XML developers like me. The book covers wide range of topics. The book is an excellent hands on guide to build voice applications with Voice XML 2.0. I liked the VUI design tips throughout the book. Great job!

This book is an excellent resource for a VoiceXML developer. It covers a wide range of topics in detail and has some excellent VUI design tips. I love the cross reference of voice technology companies and the services that they provide.

This is the best VoiceXML book I've seen. Most VoiceXML books try to do too much: talk about voice hardware, telephony, the history of voice, tts, as well as be a VoiceXML reference. The weakness of these books is that one or more of these sections reveals that the authors do not really command the knowledge needed to make these sections useful. This book also attempts to do these things, but for the most part is able to carry it off.

If you're looking for a reference, this is the book to get. The reference section is current VoiceXML 2.0 (October 2001), which is an advantage in and of itself. But the real strength of the reference section is its depth. Each element, (e.g., , , ) has an entry for syntax (how to invoke the element), a description (what the element is used for), a thorough discussion of its attributes (that is, a description of the attribute), a usage statement (the elements parents and children), and an example (a snipet of complete code that uses the element). The examples and discussion of attributes really set this book apart from its peers.

There is a brief discussion of the architecture of a VoiceXML app, and a couple of paragraphs discussing the differences between VoiceXML 1.0 and 2.0.

The book also gives, contrary to my expectations, a history of the voice industry, a history of VoiceXML, and a discussion of players in the industry. What makes this book's treatment of these topics unusual is that the authors (particularly Kunins, I suspect) actually know these fields. I don't normally want these sections in a reference book (it just adds bulk around the section I really want) but I found them quite compelling here. I learned quite a bit from reading them.

The book also contains sections on Dynamic VoiceXML, Security, Voice App Life Cycle, VUI Design, the Future of VoiceXML, and a case study. I haven't read these sections yet, so I can't comment on them. I do know, however, that the sections I have read are sufficiently superior to make this THE VoiceXML book on their own.

If I were to criticize the book, I would fault the authors' lavish praise of TellMe (this is minor and not unexpected) and the examples in the reference section. The examples are quite good for someone learning VoiceXML, and the authors are commended for including them. The fault (albeit a minor one) is that they are fairly vanilla. So, while I would have preferred more examples, I concede that such examples would make the book much larger and the inclusion of "advanced" examples to the exclusion of "canonical" examples would have made them less useful to developers learning VoiceXML.

Overall, if you are going to own one VoiceXML reference, THIS should be that one.

This is a summary of the full review available at:
http://voicexmlplanet.com/reviews/vxmlbook.html

In short, this is the VoiceXML book I wish I had written. The authors have produced a comprehensive title that includes gems that could only have originated from masters of the craft.

My only complaint is that the book is a bit too biased towards Tellme (one of the authors is an employee), but this can be forgiven based on the quality and depth of the content.

My judgement is that this book is the most well rounded in-depth book on the topic that's been published to date. I am very happy with the mix of content, summaries of important concepts such as linguistics, speech recognition, and speech synthesis, as well as the in-your-face examples and complete reference. In fact, I liked it so much that I will probably be using it as a standard reference in my company's VoiceXML training course.

I was mislead by the accompanying great reviews for this book. Having bought and read the book I find that it serves more as a reference than to illustrate how VoiceXML can be used through example applications. But I should admit though that this book does a good job of serving as a reference. I also bought "VoiceXML: 10 Projects to Voice-Enable your system" that helped me to come up to speed to do a VoiceXML project.

I used this guide for my Word Expert exam and passed. It's comprehensive enough to double as an intermediate course in Word. Unlike other study guides, it will definitely increase your productivity in Word. That said, the authors did leave me scratching my head over at least three objectives--they have a bad habit of skimming over advanced features, like forms, for which you'll need a third-party manual to figure out properly. That certainly detracts from one's confidence. The handling of Word's graphic/drawing features is only cursory and they stop short of suggesting logical solutions that would definitely come in handy during the exam--using tables to line up graphics next to bulleted lists, for example. For something as specific as an exam study guide, this is crucial. Also, though it wasn't a problem for me, there are no practice documents provided (the small download from the Sybex site is a joke) and they fully expect you to have to hand a cache of unformatted Word documents of all varieties as you work through this book--this wastes a lot of valuable study time. A major oversight on the publisher's part.

We have used this book for over a year and have found it to be not only a study guide, but a good reference book. Our students have obtained results that we are proud of. I recommend this book if you are serious about taking you MOUS and Master certification.

I thought this book prepared me for the MOUS exam very well. The information is direct and exact. I look forward to other books by Gini Courter.

This Microsoft approved courseware is the ticket to achieving certification in either the core or expert Word 2000 exams. This book covers everything from using styles and templates to creating macros and generating reference documents. The information is clearly explained, logically sequenced, and surprisingly concise! You will find a comprehensive list of Mous objectives needed to pass the exam, and advice on how to best prepare for the test. No matter what level user you are, working through the exercises in this book will give you the confidence and know how you need to breeze through the exam. Even if you think you are a proficient user of Word, after reviewing this study guide you will likely find that the methods you have used are neither the most efficient, nor the most effective. Thus, I would recommend this book simply as a tool for improving your Word skills, regardless of whether professional certification is your ultimate goal.

After reading this book cover to cover and doing the hands on excercises, I passed both MS exams. If you know everything in this book, you KNOW Word. I wish every Office 2000 application had a Study Guide from these authors.

I have definitely come to respect the Wrox writers. Whenever I am in need of additional assistance, I look to these books first. The Access 2007 VBA Programmers Guide has everything I need in it and is written in an easy to follow manner. My skill level is just above beginner, but there are sections of the book for more advanced programming that I have not looked at. I highly recommend all books by Wrox (I have used their SharePoint books extensively).

This book delivers exactly what it promises - namely, to provide the reader with the necessary tools to use VBA against the various Access 2007 object models to amplify the capabilities of a custom Access 2007 solution. You will be shown the differences between using the DAO and ADO data access technologies, as well as the costs and benefits of using the older mdb file types versus the new accdb and project-related adp file types. A cogent explanation of the additional security features embedded in Access 2007 is also nicely covered.

The authors present a broad coverage of the subject matter which is amplified by their substantial real world experience - a nice benefit considering the myriad of texts that simply offer a better organized rehash of the help files.

A final comment will address the number of helpful sidebars presented in the text dealing with such issues as: using the "SQL Server Profiler", how to programmatically add, delete, and modify registry entries to persist user related variables; and receiving insider's expert information on undocumented legacy functionality.

An excellent text for what it sets out to accomplish.

This books was a TREMENDOUS help in writing a Human Resources application for my company. I'm no programmer--but this book helped me a great deal with some of the VB that was needed for the database. I did also rely on the internet a lot but this was a handy tool that covered a majority of the basics--the internet was for more advanced scripting. I highly recommend the book for those who work with Access often...and even for those who want to take advantage of the cool things code will enable you to do.

Access 2007 VBA is a great book for experienced and novice programmers alike. It is thoroughly detailed and yet covers the VBA basics at the beginning. What I like about this book is that it covers details that other books seem to always miss. This would include Microsoft Office integration. Or, in other words, the code that lets you work with other Office applications like manipulating Excel from Access or Word from Access. It also goes into working with Outlook and even SharePoint, which are two of the hardest to find information on when working with Access VBA. I am finding this book to be a great addition to my library and I believe you will too.


Bob Larson
Access World Forums Super Moderator
Utter Access VIP

I've been using Access off and on since Windows 95 and Access 2. This is absolutely one of the best texts on VBA I have read. Examples are clear, and appropriate; and explainations are complete without being longer than the need to be. The coverage of Access 2007's new features appears to be right on the money.