| Overview
For all the buzz about trendy IT techniques, data processing is
still at the core of our systems, especially now that enterprises
all over the world are confronted with exploding volumes of data.
Database performance has become a major headache, and most IT
departments believe that developers should provide simple SQL code
to solve immediate problems and let DBAs tune any "bad SQL" later.
In The Art of SQL, author and SQL expert Stephane Faroult
argues that this "safe approach" only leads to disaster. His
insightful book, named after Art of War by Sun Tzu, contends that
writing quick inefficient code is sweeping the dirt under the rug.
SQL code may run for 5 to 10 years, surviving several major
releases of the database management system and on several
generations of hardware. The code must be fast and sound from the
start, and that requires a firm understanding of SQL and relational
theory.
The Art of SQL offers best practices that teach
experienced SQL users to focus on strategy rather than specifics.
Faroult's approach takes a page from Sun Tzu's classic treatise by
viewing database design as a military campaign. You need knowledge,
skills, and talent. Talent can't be taught, but every strategist
from Sun Tzu to modern-day generals believed that it can be
nurtured through the experience of others. They passed on their
experience acquired in the field through basic principles that
served as guiding stars amid the sound and fury of battle. This is
what Faroult does with SQL.
Like a successful battle plan, good architectural choices are
based on contingencies. What if the volume of this or that table
increases unexpectedly? What if, following a merger, the number of
users doubles? What if you want to keep several years of data
online? Faroult's way of looking at SQL performance may be
unconventional and unique, but he's deadly serious about writing
good SQL and using SQL well. The Art of SQL is not a
cookbook, listing problems and giving recipes. The aim is to get
you-and your manager-to raise good questions.
Editorial ReviewsProduct DescriptionFor all the buzz about trendy IT techniques, data processing is still at the core of our systems, especially now that enterprises all over the world are confronted with exploding volumes of data. Database performance has become a major headache, and most IT departments believe that developers should provide simple SQL code to solve immediate problems and let DBAs tune any "bad SQL" later. In "The Art of SQL," author and SQL expert Stephane Faroult argues that this "safe approach" only leads to disaster. His insightful book, named after Art of War by Sun Tzu, contends that writing quick inefficient code is sweeping the dirt under the rug. SQL code may run for 5 to 10 years, surviving several major releases of the database management system and on several generations of hardware. The code must be fast and sound from the start, and that requires a firm understanding of SQL and relational theory. "The Art of SQL" offers best practices that teach experienced SQL users to focus on strategy rather than specifics. Faroult's approach takes a page from Sun Tzu's classic treatise by viewing database design as a military campaign. You need knowledge, skills, and talent. Talent can't be taught, but every strategist from Sun Tzu to modern-day generals believed that it can be nurtured through the experience of others. They passed on their experience acquired in the field through basic principles that served as guiding stars amid the sound and fury of battle. This is what Faroult does with SQL. Like a successful battle plan, good architectural choices are based on contingencies. What if the volume of this or that table increases unexpectedly? What if, following a merger, the numberof users doubles? What if you want to keep several years of data online? Faroult's way of looking at SQL performance may be unconventional and unique, but he's deadly serious about writing good SQL and using SQL well. "The Art of SQL" is not a cookbook, listing problems and giving recipes. The aim is to get you-and your manager-to raise good questions. |
Other Readers Also Read | Top Sellers in This Category | Browse Similar Topics | | | Top Level Categories:Sub-Categories: | | | | |
Reader Reviews From Amazon (Ranked by 'Helpfulness') Average Customer Rating: based on 16 reviews. An excellent book to read after you think you know databases, 2008-07-14 Reviewer rating: This is a book in a somewhat-similar vein to Effective C++: 55 Specific Ways to Improve Your Programs and Designs (3rd Edition) (Addison-Wesley Professional Computing Series): it spends most of its time shining light on the dark nooks and crannies of database design and query optimization, and assumes that you've already at least learned that those dark nooks and crannies exist.
It is also written with the database programmer in mind, rather than the database administrator. There are not many books written for us, and I'm really pleased that one of them is a book this excellent. | Excellent, 2008-01-20 Reviewer rating: This book is very well written and goes into depth on the practical reasons behind best-practices as well as real-world examples. | This is the book to have if you want to discover better practices for your SQL , 2007-03-14 Reviewer rating: This book review was submitted by a Roanoke Valley SQL Server Users Group member as part of the Book Review Program.
Reviewed by Jerry Ellis
The Art of SQL does not fall into the trap of becoming "just another reference" for SQL users. It tackles real world problems with the point of view that you know how to write SQL code, but may need help in the proper tactics to most effectively handle them. What is refreshing is that it does not say here is a piece of code that will do this...it says, that may work, but here is a better way and why.
This is the book to have if you want to discover better practices for your SQL.
Jerry Ellis
| Not practical, 2007-01-08 Reviewer rating: I'm torn in giving stars to this book. On the one hand there a number of fascinating topics covered, topics not found in other books in my library. They tend to be of a quite academic nature, discussing the internals of how the optimizer and the DBMS engine work. From that standpoint this book would earn 5 stars.
On the other hand, I purchased the book because I have real-world problems to solve in my job. Despite what the quotes on the back cover and first pages say, virtually nothing covered in this book is of any value in solving real-world problems. The book introduces what seems like a promising new sql construct or optimization idea, describes it in detail, and then unfailingly proceeds to state all the disadvantages of using the new idea and concludes that you shouldn't bother with it. I was interested in finding new techniques to apply to real-world problems, and came away instead with a long list of new techniques to forget about. From a practical standpoint this book would earn 1 star.
So overall I give it 3 stars, an interesting read, but of little value on the job. | Disappointing, 2006-12-24 Reviewer rating: I originally really liked the idea of comparing database design to the ancient "Art of War" classic, but the more I read the book, the more annoying and overly cute this tactic became.
Amongst all the verbiage there appears to be really useful information, but extracting that information became too much work for me and I gave up on this book. And there were almost no concrete examples or case studies to back anything up.
So far the most important book I've read is Sql Tuning by Dan Tow. It takes some work, but it is very, very worth it. Try that one instead. |
Some information above was provided using data from Amazon.com. View at Amazon > |
| |
|
|
