Afbeelding 1 van 3
AFGELOPEN
The Art of SQL
Objectstaat:
Prijs:
US $7,69
OngeveerEUR 7,20
Verzendkosten:
Bevindt zich in: Carlstadt, New Jersey, Verenigde Staten
Levering:
Geschatte levering tussen vr, 28 jun en wo, 3 jul tot 43230
Retourbeleid:
30 dagen om te retourneren. Koper betaalt voor retourzending. Details bekijken- voor meer informatie over retourzendingen
Betalingen:
Winkel met vertrouwen
Verkopergegevens
- 98,9% positive feedback
Ingeschreven als zakelijke verkoper
De verkoper neemt de volledige verantwoordelijkheid voor deze aanbieding.
eBay-objectnummer:305544275548
Specificaties
- Objectstaat
- Release Year
- 2006
- Book Title
- The Art of SQL
- ISBN
- 9780596008949
- Subject Area
- Computers
- Publication Name
- Art of Sql
- Publisher
- O'reilly Media, Incorporated
- Item Length
- 9.2 in
- Subject
- General, Programming Languages / Sql, Databases / General
- Publication Year
- 2006
- Type
- Textbook
- Format
- Perfect
- Language
- English
- Item Height
- 1.1 in
- Item Weight
- 23.2 Oz
- Item Width
- 7 in
- Number of Pages
- 367 Pages
Over dit product
Product Identifiers
Publisher
O'reilly Media, Incorporated
ISBN-10
0596008945
ISBN-13
9780596008949
eBay Product ID (ePID)
50870655
Product Key Features
Number of Pages
367 Pages
Publication Name
Art of Sql
Language
English
Subject
General, Programming Languages / Sql, Databases / General
Publication Year
2006
Type
Textbook
Subject Area
Computers
Format
Perfect
Dimensions
Item Height
1.1 in
Item Weight
23.2 Oz
Item Length
9.2 in
Item Width
7 in
Additional Product Features
Intended Audience
Scholarly & Professional
LCCN
2007-270059
Dewey Edition
22
Illustrated
Yes
Dewey Decimal
005.13/3
Table Of Content
Dedication;Preface; Why Another SQL Book?; Audience; Assumptions This Book Makes; Contents of This Book; Conventions Used in This Book; Using Code Examples; Comments and Questions; Safari® Enabled; Acknowledgments;Chapter 1: Laying Plans; 1.1 The Relational View of Data; 1.2 The Importance of Being Normal; 1.3 To Be or Not to Be, or to Be Null; 1.4 Qualifying Boolean Columns; 1.5 Understanding Subtypes; 1.6 Stating the Obvious; 1.7 The Dangers of Excess Flexibility; 1.8 The Difficulties of Historical Data; 1.9 Design and Performance; 1.10 Processing Flow; 1.11 Centralizing Your Data; 1.12 System Complexity; 1.13 The Completed Plans;Chapter 2: Waging War; 2.1 Query Identification; 2.2 Stable Database Connections; 2.3 Strategy Before Tactics; 2.4 Problem Definition Before Solution; 2.5 Stable Database Schema; 2.6 Operations Against Actual Data; 2.7 Set Processing in SQL; 2.8 Action-Packed SQL Statements; 2.9 Profitable Database Accesses; 2.10 Closeness to the DBMS Kernel; 2.11 Doing Only What Is Required; 2.12 SQL Statements Mirror Business Logic; 2.13 Program Logic into Queries; 2.14 Multiple Updates at Once; 2.15 Careful Use of User-Written Functions; 2.16 Succinct SQL; 2.17 Offensive Coding with SQL; 2.18 Discerning Use of Exceptions;Chapter 3: Tactical Dispositions; 3.1 The Identification of "Entry Points"; 3.2 Indexes and Content Lists; 3.3 Making Indexes Work; 3.4 Indexes with Functions and Conversions; 3.5 Indexes and Foreign Keys; 3.6 Multiple Indexing of the Same Columns; 3.7 System-Generated Keys; 3.8 Variability of Index Accesses;Chapter 4: Maneuvering; 4.1 The Nature of SQL; 4.2 Five Factors Governing the Art of SQL; 4.3 Filtering;Chapter 5: Terrain; 5.1 Structural Types; 5.2 The Conflicting Goals; 5.3 Considering Indexes as Data Repositories; 5.4 Forcing Row Ordering; 5.5 Automatically Grouping Data; 5.6 The Double-Edged Sword of Partitioning; 5.7 Partitioning and Data Distribution; 5.8 The Best Way to Partition Data; 5.9 Pre-Joining Tables; 5.10 Holy Simplicity;Chapter 6: The Nine Situations; 6.1 Small Result Set, Direct Specific Criteria; 6.2 Small Result Set, Indirect Criteria; 6.3 Small Intersection of Broad Criteria; 6.4 Small Intersection, Indirect Broad Criteria; 6.5 Large Result Set; 6.6 Self-Joins on One Table; 6.7 Result Set Obtained by Aggregation; 6.8 Simple or Range Searching on Dates; 6.9 Result Set Predicated on Absence of Data;Chapter 7: Variations in Tactics; 7.1 Tree Structures; 7.2 Representing Trees in an SQL Database; 7.3 Practical Implementation of Trees; 7.4 Walking a Tree with SQL; 7.5 Aggregating Values from Trees;Chapter 8: Weaknesses and Strengths; 8.1 Deceiving Criteria; 8.2 Abstract Layers; 8.3 Distributed Systems; 8.4 Dynamically Defined Search Criteria;Chapter 9: Multiple Fronts; 9.1 The Database Engine as a Service Provider; 9.2 Concurrent Data Changes;Chapter 10: Assembly of Forces; 10.1 Increasing Volumes; 10.2 Data Warehousing;Chapter 11: Stratagems; 11.1 Turning Data Around; 11.2 Querying with a Variable in List; 11.3 Aggregating by Range (Bands); 11.4 Superseding a General Case; 11.5 Selecting Rows That Match Several Items in a List; 11.6 Finding the Best Match; 11.7 Optimizer Directives;Chapter 12: Employment of Spies; 12.1 The Database Is Slow; 12.2 The Components of Server Load; 12.3 Defining Good Performance; 12.4 Thinking in Business Tasks; 12.5 Execution Plans; 12.6 Using Execution Plans Properly; 12.7 What Really Matters?;PHOTO CREDITS;About the Author;
Synopsis
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., 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 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., Enterprises throughout the world are confronted with exploding volumes of data, and many IT departments are looking for quick solutions. This insightful book demonstrates that since SQL code may run for 5 to 10 years, and run on different hardware, it must be fast and sound from the start. Expert Stephane Faroult offers SQL best practices and relational theory that force you to focus on strategy rather than specifics., 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.
LC Classification Number
QA76.73.S67F376 2006
ebay_catalog_id
4
Copyright Date
2006
Objectbeschrijving van de verkoper
De verkoper neemt de volledige verantwoordelijkheid voor deze aanbieding.
eBay-objectnummer:305544275548
Verzending en verwerking
Objectlocatie:
Carlstadt, New Jersey, Verenigde Staten
Wordt verzonden naar:
Afghanistan, Albanië, Algerije, Andorra, Angola, Anguilla, Antigua en Barbuda, Argentinië, Armenië, Aruba, Australië, Azerbeidzjan, Bahama's, Bahrein, Bangladesh, België, Belize, Benin, Bermuda, Bhutan, Bolivia, Bosnië en Herzegovina, Botswana, Brazilië, Brunei Darussalam, Bulgarije, Burkina Faso, Burundi, Cambodja, Canada, Centraal-Afrikaanse Republiek, Chili, China, Colombia, Costa Rica, Cyprus, Democratische Republiek Congo, Denemarken, Djibouti, Dominicaanse Republiek, Duitsland, Ecuador, Egypte, El Salvador, Equatoriaal-Guinea, Eritrea, Estland, Ethiopië, Fiji, Filipijnen, Finland, Frankrijk, Gabon, Gambia, Georgië, Ghana, Gibraltar, Grenada, Griekenland, Groenland, Guatemala, Guinee, Guinee-Bissau, Guyana, Haïti, Honduras, Hongarije, Hongkong, IJsland, Ierland, India, Indonesië, Israël, Italië, Ivoorkust, Jamaica, Japan, Jemen, Jordanië, Kaaimaneilanden, Kaapverdische eilanden, Kameroen, Kazachstan, Kenia, Kirgizië, Kiribati, Koeweit, Kroatië, Laos, Lesotho, Letland, Libanon, Liberia, Liechtenstein, Litouwen, Luxemburg, Macau, Macedonië, Madagaskar, Malawi, Maldiven, Maleisië, Mali, Malta, Marokko, Mauritanië, Mauritius, Mexico, Moldavië, Monaco, Mongolië, Montenegro, Montserrat, Mozambique, Namibië, Nauru, Nederland, Nepal, Nicaragua, Nieuw-Zeeland, Niger, Nigeria, Noorwegen, Oeganda, Oezbekistan, Oman, Oostenrijk, Pakistan, Panama, Papoea-Nieuw-Guinea, Paraguay, Peru, Polen, Portugal, Qatar, Republiek Congo, Roemenië, Rwanda, Saint Kitts en Nevis, Saint Lucia, Saint Vincent en de Grenadines, San Marino, Saudi-Arabië, Senegal, Servië, Seychellen, Sierra Leone, Singapore, Slovenië, Slowakije, Solomoneilanden, Spanje, Sri Lanka, Suriname, Swaziland, Tadzjikistan, Taiwan, Tanzania, Thailand, Togo, Tonga, Trinidad en Tobago, Tsjaad, Tsjechië, Tunesië, Turkije, Turkmenistan, Turks- en Caicoseilanden, Uruguay, Vanuatu, Vaticaanstad, Verenigd Koninkrijk, Verenigde Arabische Emiraten, Verenigde Staten, Vietnam, Wallis en Futuna, Westelijk Samoa, Zambia, Zimbabwe, Zuid-Afrika, Zuid-Korea, Zweden, Zwitserland
Uitgesloten:
APO/FPO, Amerikaanse protectoraten, Barbados, Frans-Guyana, Frans-Polynesië, Guadeloupe, Libië, Martinique, Nieuw-Caledonië, Oekraïne, Russische Federatie, Réunion, Venezuela
| Verzending en verwerking | Tot | Service | Levering*Zie opmerkingen over levering |
|---|---|---|---|
| Gratis verzending | Verenigde Staten | Standard Shipping | Geschatte levering tussen vr, 28 jun en wo, 3 jul tot 43230 |
| US $8,99 (ongeveer EUR 8,42) | Verenigde Staten | Expedited Shipping | Geschatte levering tussen do, 27 jun en di, 2 jul tot 43230 |
| Verwerkingstijd |
|---|
| Wordt doorgaans binnen 2 werkdagen na ontvangst van betaling verzonden. |
| Belasting |
|---|
| Er kunnen belastingen van toepassing zijn tijdens Betalen. Meer weten?Lees meer over het betalen van belastingen op eBay-aankopen. |
Btw voor objectnr.305544275548
Btw voor objectnr.305544275548
Verkoper berekent btw op objecten die naar de volgende staten worden verzonden:
| Staat/provincie | Btw-tarief |
|---|
Retourbeleid
| Nadat u het object hebt ontvangen, kunt u contact opnemen met de verkoper binnen | Terugbetaling wordt verstrekt als | Kosten voor retourzending |
|---|---|---|
| 30 dagen | Geld terug | Koper betaalt voor retourzending |
De koper is verantwoordelijk voor de kosten van de retourzending.
| Details retourbeleid |
|---|
| Retourzendingen geaccepteerd |
Betalingsgegevens
Betalingsmethoden
Ingeschreven als zakelijke verkoper
Feedback verkoper (116.997)
n***l (723)- Feedback gegeven door koper.
Afgelopen maand
Geverifieerde aankoop
Quick ship and as described.
p***t (413)- Feedback gegeven door koper.
Afgelopen maand
Geverifieerde aankoop
As advertised, prompt delivery.
r***7 (323)- Feedback gegeven door koper.
Afgelopen maand
Geverifieerde aankoop
A++