5 comments about MySQL: Building User Interfaces (Landmark).

1. Let me say this right away: This is a good book. If you already know your way around MySQL and have at least a basic knowledge of C, you'll very quickly get up to speed in creating a MySQL GUI (GTK+) application for your co-workers or your client.
   The introduction lays out some of the foundations, and the reader is warned that some skills are required before delving deeper into the book: Basic knowledge of C, SQL, Linux are all required to gain anything from this book. Some experience in VB, Delphi or other form-based IDEs will also give you a good start on the book.
   The first section of the book gives a good run-down on MySQL, GTK+ and Glade. There are a few non-critical errors in the text (stating that a MySQL table is limited to 50 mio. records; claiming that Qt is not free, although the Qt/X11 is released under the GPL). The chapters on GTK+ also give the reader the first taste of the author's preference on using page upon page of commented source, rather than explanatory body text.
   The second section is a walk-through of three Real-world implementations. The first is a relatively simple order entry application; the second a commissions calculation application and the third a fairly complex report generator. In all three examples, the focus is primarily on Glade and GTK+, and very little mention is made of MySQL.
   The third section is a short discussion on using the XML files generated by Glade, which may -- in some very specific cases - allow the programmer to make changes to an application without recompiling a project. This discussion really is too short, and I wonder whether the reader might be confused more than helped by this chapter. These pages could have been of much better use if the author had spent some more time discussing security issues in MySQL and applications, something which this books sorely lacks. There is some discussion on the subject, but it's much too short and general.
   One thing I really like about the examples is the "running commentary" on how to distribute programs, moving from a simple "copy the executable" over "make install" and ending up at "building an RPM".
   I like examples, and a good tutorial should contain a lot of them. Some of the code examples in the book are very good -- those where a small section of a program is shown, and each important line of code is emphasized and explained. In this book, the author has chosen to give us page up and page down of program listings, which, although well commented in-line, make for extreme terse reading. More than half the book is comprised of program listings, and that's not counting the last 150+ pages making up the appendix, consisting solely of program listings. I have serious doubts that anyone will ever be reading these.
   The title of the book is, unfortunately, very badly chosen. "MySQL" suggests that you can only use this book with the MySQL DBMS, even though many of the SQL examples are really quite general in scope; "Building User Interfaces" suggests that this book contains a general discussion on UI, while it is in fact very heavily centered on GTK+. The layout of the front page also suggests that the main focus on the book is MySQL, which is not true -- only about 25% of the contents are set off for discussing MySQL, the rest of the book is about Glade and GTK.
   If you're coming from a Windows/MS-Access background and wish to know more about writing GUI applications for MySQL, program deployment, this book is definitely for you. If you've never worked with MySQL (or any other SQL database), you should get some more experience before getting this book.
   I'm giving five stars for the contents minus one for a misleading title page.



2. Mathew Stucky has written an interesting book on building Graphical User Interfaces that interface to the MySQL database. As such, it is a nice follow-on to MySQL by Paul Dubois. This book seems to be primarily aimed at VB developers (or similar GUI development frameworks) who wish to build GUI applications using MySQL as the backend. While MySQL runs on a wide range of different platforms, being an open-source product, it is extremely popular on Linux.

   The book tackles many different user interface projects in a consistent manner, starting with a problem definition, followed by designs of the UI and database, and concluding with an analysis of the application. The main complaint I had with the book is that it really discusses only one approach to building user interfaces to MySQL, completely ignoring the web interface, which could be built with PHP, JSPs, or even applets. Thus the title is somewhat misleading. Finally, the reader does need a fairly hefty background before starting this book.




3. This book will guide you very well through learning the wrong database.

   Yes, I've read the book (long ago). It helped me to learn MySQL. It even made me an advocate of MySQL. But I didn't know the first thing about what makes a database work. I was following the masses of new web developers, ignorantly flocking to MySQL.

   If you need fantastic speed, rock-solid reliability and -- more importantly -- a true understanding of how real RDBMS systems work, learn and use PostreSQL. It runs circles around MySQL! (We use it to support web services in 20 countries).

   PostgreSQL will look far better on your resume than will MySQL. When I see PostgreSQL listed on a candidate's resume, I know (if the candidate is truly postgres-savvy) s/he can be counted on to work with virtually any database we support.




4. I've been working through this book for quite some time, and now that I've extracted all i can I have to declare myself delighted with it. The examples are good, deep enough to convey the lessons but shallow enough that not too much is irrelevant. I now have, as the author promised, several applications that will compile easily under both linux and win32. If i can fault the book at all , my only reservation is that is would have been nice to see all the necessary software included on the cd. Downloading all of the required applications and libraries (particularly for windows) led to a treasure hunt accross the web. That aside I would recommend this book to anyone who is not new to programming and databases, a little prior knowledge will be required as this is definately not a complete beginners book.



5. I'm not sure where all of these 5 and 4 stars are coming from. This book is absolutely horrible at addressing UI design. Half of the book is C code for GTK applications that could have been made available on a companion disk or on the website. And most of Stucky's explanation of things comes in the form of very brief comments embedded within the code. Lots of typos. Lots of butchered examples. No general GUI concepts covered. No coverage of multithreading issues. You're basically getting three non-real-world examples' code bound in a book and hardly any coverage of general user interface design concepts and ideologies. The title should have been "Beginner's Guide to Using GTK with MySQL and Glade".

5 comments about MySQL and mSQL.

1. Simply the best MySQL intro book. If you have no MySQL experience I believe you have no idea where to start from and this book is a perfect tutorial that guide MySQL newbie step by step to more and more complicated aspects of MySQL. Even if almost 1/3 of the book is about programming MySQL using different languages, you will find enough information to get basic MySQL experience, have a clear understanding of all MySQL concepts and be prepared to read (and understand) MySQL reference books ( You will need them anyway :-) )

   Even when you finish to read this book
   it will serve you as good SQL (mSQL and MySQL dialects) reference.

   Conclusion: this is your first MySQL book! I think the second will be MySQL Reference Book.




2. This books provides a good all around introduction to databases, SQL and the mSQL and MySQL database servers. It tends to favor MySQL a bit more, but this seems appropriate given that MySQL is now far more advanced than mSQL.

   It also serves as a pretty good reference for both servers (though, by no means a complete one). It explains some database building basics, as well as what 2NF and 3NF mean (and how to make your database 3NF). It contains several useful chapters on different APIs to MySQL and mSQL including a very helpful introduction to the Perl DBI.

   I still find the reference pages pretty helpful, but for people looking for an advanced reference, I'd say look elsewhere (perhaps "Managing and Using MySQL" (ASIN 0596002114)).

   If you're just learning SQL or MySQL, this is a great book!




3. The books was my first introduction to MySQL ( I never read anything about mSQL out of choice) and I felt it started of well, but as I got further the book lacked depth both in examples and content. The second half is more like a reference manual probably good for someone with prior knowledge. I guess O'relliy could do better having more detailed examples and an online reference code / cd with ready examples from the book.



4. Do NOT buy any other book on MySQL. You will end up tossing others aside and buying this one. As others have said, chapter 2 gives the absolute best discussion of normalization ever. It is required reading of new staff in my shop. This book is always within arms reach when I am coding. Do yourself a big favor and buy it NOW.



5. I have had this book for 3 years now and it is still on my "easy-access bookshelf". I use MySQL and can't comment on the mSQL portion. I can't claim that it is the best book to learn from, but it was adequate for me at the time...the mere fact that I still use this book so frequently is enough for me to recommend anyone to buy it as a MySQL reference book.

1 comments about The Best Damn Exchange, SQL and IIS Book Period (Best Damn) (Book Period).

1. This book should be titled "The Worst Damn...".
   
   I have only read the SQL section up to this point but this book is only useful for intermediate level DBAs and if you are an intermediate DBA you wouldn't need the book so I'm not sure where it fits into the hierarchy of information but it defiantly is not for beginners or anyone coming from a different RDBMS.
   
   My biggest complaint is that the book in not organized progressively building your knowledge upon what you read in a previous section. The norm is to introduce a specific feature, for example stored procedures, without any prior definition, the author just tells you out of the blue to use stored procedure xyz and never explains what a stored procedure is. This happens over and over again and you will quickly find yourself frustrated because you can't follow along as you have no previous knowledge of what the author is talking about.
   
   There are no installation instructions other than to tell you that you should only install the necessary modules for your environment. There is no mention of how to create a database; the author just starts talking about roles, security, authentication mode, etc.
   
   Again, I'm not sure what anyone could get out of this book because you have to already have a sound understanding of SQL to follow along and if you already have a sound understanding of SQL these guys aren't telling you anything you don't already know.
   
   I hope the sections on Exchange and IIS are better.

3 comments about Mastering phpMyAdmin for Effective MySQL Management 2e.

1. The purpose of this book by Marc Delisle is to teach you how to use phpMyAdmin, which is a popular open source program for working with a MySQL database using the phpMyAdmin user-friendly graphic interface. Most PHP programmers use MySQL for their database needs because these two technologies work so well together. For those who have not yet worked with phpMyAdmin and MySQL, this book will help you get up and running quickly. And for those programmers who have taught themselves to use phpMyAdmin by trial and error, this book will introduce and explain those features you may have missed.
   
   The author begins with an introduction to phpMyAdmin. He covers the main features and some history of the program. After that, he jumps right in to the installation, configuration and security issues for the Linux, Apache and IIS servers. Of course, if you are using phpMyAdmin with your web host account, you may not have much control over these issues. Once the program is installed, he explains the user interface and discusses those easy-to-use features that make this program so popular.
   
   Delisle starts with the basic tasks such as creating databases and setting up tables. He explains the different types of data, table fields and the various choices you have when performing many tasks. Next, he shows you how to move tables between databases and how to backup, copy and move databases between servers. Although the user-friendly graphic interface is what makes phpMyAdmin so nice, you may at some time need to use the SQL commands alone. The author covers the most common tasks you may encounter. Finally, he moves on to more advanced issues such as administrative tasks and generating database reports and documentation.
   
   Marc Delisle is a developer and project administrator for the phpMyAdmin project. He also teaches at the College de Sherbrooke, Quebec, Canada.



2. I've got a review copy of the phpMyAdmin 2.8 book as well as the previous edition of this book. The old edition already was rather comprehensive and had all the features that phpMyAdmin has cleary laid out.
   
   Still, the layout of the new edition improved a notch, this is a nice update. While you probably won't need the book if you already have the old edition, it is a nice book to help you get out the most of phpMyAdmin.



3. If you don't like command-line interface with your computer, phpMyAdmin is a great tool! And if you want to learn the right way to interact with phpMyAdmin, this book is your perfect resource!
   I stumbled upon a phpMyAdmin screencast by DeLisle at a conference. His calm and collected presentation style along with a great clarity for instruction is repeated in this book.
   Mastering phpMyAdmin has enabled me to move out of my limited comfort zone with database management in general. The book is clearly laid out to give you step-by-step instructions to make a database work for you.
   I highly recommend this book, and DeLisle's Creating your MySQL Database: Practical Design Tips and Techniques as well. They are great books!

5 comments about MCSE SQL 2000 Administration Exam Cram (Exam: 70-228).

1. This book gave me the extra pieces of information I needed to pass the exam. SQL 2000 ROCKS!



2. I passed 70-228 on my first attempt, using this book in conjunction with Transcender and Books Online as my primary study resources.

   You won't get all the information you need to pass the real test from this book, but that is not its intent. It works well when used for what it is marketed as, which is a "cram" resource to supplement a sound knowledge of SQL Server 2000 administration. Especially useful for me were the practice questions, the practice test at the end, and the screenshots of Enterprise Manager dialogs. Good to have in the hours immediately before the test!

   The contents have a few errors, including referring to the model database as "modal" throughout the book, but that doesn't detract too much from the overall utility of the book.

   All in all, a good investment, considering the cost of each attempt on the real test.

   RD




3. No, no, no.. This book is a waste of time. It gives an IN DEPTH step by step, excrutiatingly detailed how-to examples on using the installation wizard, and then glosses over the more important details that actually appear on the exam (like the C2 auditing and analyzing the SQL 2000 performance counters). If you're familiar at all with the software, this book has little or nothing to offer you in terms of actually test preparation. Microsoft assumes everybody taking the certification exams already knows when to click the next button.. Don't waste your time or money on this. The Dummies book is much better.



4. I read the entire book in 2 days... there is nothing in the book to actually remember... No concepts are described... all you see in this book are the screen shots of Enterprise Manager...
   
   Honestly I don't recommend this book. I didn't try the Microsoft press book.. If I were to choose between this book and the Microsoft press book I would go for the Microsoft press book because I am very sure that any other book will have more information than this book. This book has nothing at all.. believe me.. NOTHING to read for the test.
   
   I have used several Exam Cram books before and all of them turned out to be very useful other than this book. This book is not at all comparable with other books so use other books for your preparation.
   
   GOOD LUCK



5. This book gives you alot of facts to remember and no examples to use. The test was all configuration and security scenario questions and alot of stuff in the book was hardly covered like backup and recovery, DTS, BCP, DBCC statements, replication, maybe one question each on these. No questions at all on steps to take during installation and configuration. I will be looking for something to supplement this with..

2 comments about Test Yourself MCDBA SQL Server TM 2000 Administration (Exam 70-228).

1. This book has some good information, but it's obvious that they skipped all the steps needed to locate the errors. It's supposed to have the correct answers for test questions. However, multiple times up to chapter 7, I'm finding that the answer key is off, obviously off by getting the numbers mixed up and so on. This book can still be helpful, but it's very disappointing to find this many errors after paying good money for the book. I'd consider going to other publishers before buying again from these people.



2. This book does include all the highlights on each section. However, the layout could be improved for readability. There's an error on the questions and answers arrangement. Overall, I like the in-depth answers to all the questions, help readers to analyze questions in MS way. It's great to review this book prior to your exam for consolidation.

5 comments about Professional SQL Server 2000 Database Design.

1. I am old veteran engineer (hardware and software) working mostly alone on a new project for the .NET platform with SQL Server underneath for data. I am using Embarcadero ERStudio for database modeling. I have a great library (more than 20 titles) on relational database modeling and design; but this is the one that I keep on my desk. I am pretty much following this book step by step on my current project. The author uses the IDEF1X diagramming notation for logical design, which, quite conveniently, is what I use in ERStudio.

   This is a great guide for the experienced professional developer who may do database design only occasionally. Examples are all from the business world. The book is filled with code, which can be downloaded.

   The 606-page book has two sections: (1) logical design and (2) physical design and implementation. So far I have only completed the first section, but looking ahead it seems that this book will carry me all the way through actual testing of my finished application.

   The name suggests, perhaps improperly, a particular connection to Microsoft's SQL Server. The book addresses design and implementation issues on a general relational/SQL level; and the specific setups and interfaces (the MMC for example) of Microsoft's latest relational database, SQL Server 2000, are absent. I do not see a single SQL Server screen shot among the hundreds of illustrations. Specifics of setting up SQL Server are available in dozens of other books. This is a software engineering book, not a system administration book. Those making their first attempt at relational design will find the book a bit too challenging unless they are serious professionals.




2. Este libro no es solo para profesionales, también sirve para aquellas personas que poseen conocimientos básicos de SQL Server 2000 y de Diseño de Base de Datos y desean ampliar sus conocimientos.

   Te lleva de la mano en todo momento, desde el momento de la toma de información y las entrevistas con el cliente hasta el proceso de Diseño de la Base de Datos como tal en SQL Server 2000.

   Además utiliza un lenguaje muy cotidiano, lo cual hace el libro un poco particular.




3. My background is as an ASP developer and new dedicated DBA / Data Architect. I've done pretty extensive data modeling and implementation for several small to medium sized ASP applications. I am a big fan of the Wrox P2P series. This is my 8th Wrox purchase.

   I was disappointed in this book, but I'm having trouble putting my finger on exactly why I was disappointed. I read every word, which is rare for a technical book, but I just don't feel like I learned in the areas that I really wanted to learn. My two main goals for this read were to learn how to better build business rules into my databases and to reinforce and validate data modeling techniques I have been taught from mentors.

   Extensive coverage is given in the first half of the book to the logical design (extensive to the point of obnoxious). Tips on how to break down your notes for entities and relationships and the like are abundant. A theme I kept repeating to myself over and over as I read was that this is big-time overkill for anything other than an enterprise-scale application. I'm as big an advocate of documenting client interviews as the next guy, but come on - breaking down every paragraph looking for verbs is just overkill. There was no advice given on how to solicit valuable information. Reports are discussed, but I'm a firm believer that reports can tell you much more about an application's true value than anything else. I very much prefer to start by asking the question "What information do you need from the system to do your job better than you do today?" than to start out by asking, "What do you do all day?" I find it the only way to break users out of the paradigm that they have worked in for so long and it leads to much more innovative useful applications. Nothing like this was in the book. I learned how to go through notes that magically appear, and that reports will shed light on missed pieces of information and new pieces of functionality, but who doesn't know that that has designed a database?

   Davidson is a BIG advocate of normalization. And while there is no substitute for a well-normalized database for application stability and data integrity, Davidson advocates the breaking out of tables for the most meaningless of reasons. Those that develop applications on top of his databases much hate all the extra work he builds in. I disagree with his assertion that the database should be built to anticipate any possible changes to the user-expected data. You will spend forever trying to anticipate changes, and even longer coding over the massive database you have built. For example, in order to store a user's address, Davidson advocates a six-table structure with five joins. Are you kidding me? What coder wants to deal with all that just for the possibility that some time down the road the users may want to add Address Line 10 to the application.

   Davidson also follows an annoying pattern for demonstrating his normalization techniques. He presents a data model with problems, introduces a concept, applies the concept to the tables and comes up with a better model. This is great, except that he continues to build on the same example throughout the book. So, other than the very last model, all the ones before it are incorrect. You have to read every word in order to get to the correct answer. It makes it impossible to pick up a chapter to use as a reference, because if you create a solution similar to the one demonstrated, you will have an improperly normalized database. Fine for a book you read front to back, but not so good for a reference manual.

   The implementation details of the book were even more disappointing. Davidson is not an advocate of an N-Tier approach to coding. He believes that as many of the business rules that can be incorporated into the database should be built there. He openly says that he butts heads with his developers and system architects over this issue. I'm not surprised. While I suppose that building the business rules into the database is good for data integrity, I think the biggest advantage for the DBA is job security. I believe that a well-built database should be flexible to changes in business rules and that the data should be stored independent of those rules whenever possible. We all know rules change, and I don't like messing with a production database if I can help it. I would rather have flexibility in the model and trust my business tier coders to do their job.

   The chapters on Stored Procedures, UDFs, Triggers, and the like are too complicated for a newbie and too un-detailed for an experienced developer. I found Professional SQL Server 2000 Programming by Robert Vieira a much better reference for both the basics and best practices.

   I guess I've written enough. I still feel there is value in this book. For someone that has never designed a database before or has no formal training, it may be a good reference, but I fear it will be too complicated for a true newbie. There are valuable bits of advice and I broke out my highlighter more than once. In particular, Davidson offers some simple modes for overcoming common problems such as attribute change history.

   Three stars - I just had too many disagreements with the author to go any higher.

   -HawkeyeGK




4. This is the kind of book that will help the developer who has been working in Access and now finds the company has up sized to SQL Server. It's one of those books you add to your library that you read to make sure you have all the basics covered. I also like the fact that it gave the developer a look at the DBA side of the coin, which I'm sure will help the guy or gal who finds their the whole ball of SQL Server wax and has to do it all from developer to DBA.
   Well Worth the investment in time and money.



5. I've been reading many reviews about WROX books and people make it sound like WROX is the next O'Reilly of tech books. So when I needed a MSS-QL design book I figured I'd give them a try, especially after their good reviews on this book.

   Leave it to say I'm very dissapointed. I own well over 100 tech books and this is by far the most wordy book I've read. This extra detail of wordiness does not offer some great insight into the subject but seems to serve as a way for the author(s) to turn what should be a 250 page book into a long and boring 600 page read.

   I prefer books that get "right to the point". Theory is good and all but not in excessiveness. What it really boils down to is time, this book doubles my pacing and doesn't offer more in the line of education. If I wanted to read something big, I'll buy 'War & Peace'.

   Bigger is NOT always better.

3 comments about VB.NET & SQL Server 2000: Building an Effective Data Layer.

1. I own about 20 Wrox programming books. This is one of the more disappointing ones in my collection.

   I bought the book because I was specifically interested in "Building an Effective Data Layer" with VB.Net, i.e. implementing n-tier applications and specifically the Data Access tier. Unfortunately this important topic rarely came up in the book and when it did it was lost in the details. It does cover the SQLClient, and DataReader, ADO.Net, Data Binding and Stored Procedures. However, other books already do that.

   It never specifically covers the "Concept" of tiers, nor the strategy for implementing them (e.g. strategies for passing information between tiers, or using VB.Net's more object oriented features to implement the layers).

   The organization and emphasis was weak. The Second Chapter "The SQLClient Namespace" should have been an appendix. The very last chapter is a Case Study which involves a data layer, but the authors fail to explain the strategy and implementation of data tiers using VB .Net.

   All-in-all it was very, very disappointing.




2. Initially the book was a little overwhelming, but as our development team's competence and familiarity with .NET increased, so the later chapters became more valuable. This is especially true of the iBank Case Study, which provides a great "How To..." reference in building a complete enterprise
   application using all the elements of .NET based on multiple tiers (Presentation, Business, and Data Layers).

   The book's highly professional structure and coding techniques demonstrates the authors' deep knowledge and experience in the SQL/VB.NET domain.




3. A lost classic
   This is a great book -unfortunatly overlooked.
   A great partner to my other fave Wrox title-Proffesional VB Design patterns.

   My favorite chapters are Chapter 9 Component Services and Chapter 12 Case Study IBank
   You will have to work really hard on the case study 40hrs-80hrs + to get a real gain from this book but unlike some other Wrox books - its not over the top.

2 comments about The SQL Server 2000 Book.

1. This book is great if you need to start administering SQL Server 2000 right away. Simple, plain language and great examples and walk-throughs make this book the way to go. You also do not need to wade through hundreds of pages of "fluff" like you do with other SQL Server texts.



2. SQL Server makes up one of the fundamental building blocks of database management. Surely whatever database server your company chooses is what you should learn. It just so happens my organization chose MS SQL 2000.
   
   To make a long story relatively short, I was very new to SQL and knew very little about it. So as not to enter into the "panic-mode" I went to Amazon with hopes I could find a book on SQL 2000 with great recommendations. I think I found it in "The SQL Server 2000 Book.
   
   At first glance, the SQL language seemed very intimidating and complex to me, but it's really not all that bad. Anthony Sequeira's book had a lot to do with making it less intimidating to me. Hey if it could help a thick-head like me, I'm sure it could help you too.
   
   I would also recommend "MCSA/MCSE/MCDBA Self-Paced Training Kit: Microsoft SQL Server 2000 System Administration, 70-228, Second Edition" put out by Microsoft Press.
   
   Both books have been a tremendous help.

1 comments about Client-Server Applications with Visual FoxPro and SQL Server.

1. This book provides one of the best references available for integrating Visual FoxPro and SQL Server. There are few guides for the Visual FoxPro Developer in how to create multi-user applications in Client/Server Mode. Urwiler, Dewitt, Levy, and Charon have teamed up to write a book that fills a large gap in the VFP to SQL Server integration area. The book provides a step-by-step process that is simple enough in format to understand and basic enough to put in practice with little previous SQL Server experience. The authors begin with a quick overview of client/server, basic database design and theory before moving into the more complex tasks of upsizing and connectivity.
   
   There are plenty of code examples and appropriate illustrations. As a book targeted towards the VFP programmer the authors do a fairly good job. The four coauthors provide tips and point out problem areas and pitfalls to avoid. There are helpful hints for using GenDBC a utility program the ships with VFP to refine remote views. While the book covers the entire subject of integration well, the better features of interest are the contrast and comparing of VFP and SQL Server database architecture. Some of the book's best sections of interest include:
   
   Using SQL Server Security
   Connecting to the Database Server with Remote Views
   Working with ODBC
   Optimizing View Performance
   Connecting to the Database Server with SQL Pass-Through
   
   Once you finish reading the book, many of the your questions regarding SQL Server integration will be answered. This book is a great introduction to SQL Server. But for the more complex operations of performance tuning and optimizing, there are better books available.
   
   The book is easy to read but leans toward the technical. Be warned this is a technical book and while some technical books not only instruct but entertain. This is not one of them. This is written in a no nonsense and get-down-to-business style. If you want a light read look else where, but if you need to upsize your VFP database and do it quickly look no further.