Share
Lesezeichen setzen
The Art of SQL
Notizen
Melde dich an um eine Notiz hinzuzufügen
- Contents
- + Preface
-
+
Laying Plans
- The Relational View of Data
- + The Importance of Being Normal
- To Be or Not to Be, or to Be Null
- Qualifying Boolean Columns
- Understanding Subtypes
- Stating the Obvious
- The Dangers of Excess Flexibility
- The Difficulties of Historical Data
- Design and Performance
- Processing Flow
- Centralizing Your Data
- System Complexity
- The Completed Plans
-
+
Waging War
- Query Identification
- Stable Database Connections
- Strategy Before Tactics
- Problem Definition Before Solution
- Stable Database Schema
- Operations Against Actual Data
- Set Processing in SQL
- Action-Packed SQL Statements
- Profitable Database Accesses
- Closeness to the DBMS Kernel
- Doing Only What Is Required
- SQL Statements Mirror Business Logic
- Program Logic into Queries
- Multiple Updates at Once
- Careful Use of User-Written Functions
- Succinct SQL
- Offensive Coding with SQL
- Discerning Use of Exceptions
- + Tactical Dispositions
-
+
Maneuvering
- + Terrain
-
+
The Nine Situations
- + Small Result Set, Direct Specific Criteria
- Small Result Set, Indirect Criteria
- Small Intersection of Broad Criteria
- Small Intersection, Indirect Broad Criteria
- Large Result Set
- Self-Joins on One Table
- Result Set Obtained by Aggregation
- + Simple or Range Searching on Dates
- Result Set Predicated on Absence of Data
-
+
Variations in Tactics
- + Weaknesses and Strengths
-
+
Multiple Fronts
- + Assembly of Forces
- + Stratagems
-
+
Employment of Spies
- Photo Credits
- Index
Öffentliche Notizen (1)
gepostet von Nicolas.Wittenborn vor 11 Monate
So there are a lot of pages without any code.
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.
Teste die Closed Alpha von paperc.com
Book Details
Autoren
Stephane Faroult Stephane Faroult und Peter Robson Peter Robson
Kategorien
Computer & Internet > Programmiersprachen > SQL
Verlage
Erscheinungsjahr : 2007
Lizenz: Alle Rechte vorbehalten ©
Gelesen: 852 mal
