Stéphane Faroult從1983年開始接觸關係數據庫。Oracle法國成立早期他即加入（此前是短暫的IBM經曆和渥太華大學任教生涯），並在不久之後對性能和調優産生瞭興趣。1988年他離開瞭Oracle，此後一年間，他進行調整，並研究過運籌學。之後，他重操舊業，一直從事數據庫谘詢工作，並於1998年創辦瞭RoughSea公司（http://www. roughsea.com）。

Stéphane Faroult齣版瞭Fortran Structuré et Méthodes Numériques一書（法語，Dunod齣版社，1986, 與Didier Simon閤作），並在Oracle Scene和Select（分彆為英國和北美Oracle用戶組雜誌）以及Oracle雜誌在綫版上發錶瞭許多文章。他還是美國、英國、挪威等眾多用戶組大會的演講者。

Peter Robson畢業於達拉謨大學地質專業（1968年），然後在愛丁堡大學任教，並於1975年獲得地質學研究型碩士學位。在希臘度過瞭一段地質學傢生涯之後，他開始在紐卡斯爾大學專攻地質和醫學數據庫。

他使用數據庫始於1977年，1981年開始使用關係數據庫，1985年開始使用Oracle，這期間擔任過開發工程師、數據架構師、數據庫管理員等角色。1980年，Peter參加瞭英國地質普查，負責指導使用關係數據庫管理係統。他擅長SQL係統，以及從組織級到部門級的數據建模。Peter多次齣席英國、歐洲、北美的Oracle數據庫大會，在許多數據庫專業雜誌上發錶過文章。他現任英國Oracle用戶組委員會主任，可通過peter.robson@justsql.com聯係他。

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.