Muutke küpsiste eelistusi

E-raamat: Relational Database Programming: A Set-Oriented Approach

4.00/5 (2 hinnangut Goodreads-ist)
  • Formaat: PDF+DRM
  • Ilmumisaeg: 30-Jun-2016
  • Kirjastus: APress
  • Keel: eng
  • ISBN-13: 9781484220801
Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 34,57 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
Relational Database Programming: A Set-Oriented ApproachSuurem pilt
  • Formaat: PDF+DRM
  • Ilmumisaeg: 30-Jun-2016
  • Kirjastus: APress
  • Keel: eng
  • ISBN-13: 9781484220801
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

Tagline: Database performance through set-based development practices

Learn the best way of writing code to run inside a relational database. This book shows how a holistic and set-oriented approach to database programming can far exceed the performance of the row-by-row model that is too often used by developers who haven’t been shown a better way. 

Two styles of programming are encountered in the database world. Classical programming as taught in many universities leads to an atomic, row-oriented, and procedural style inspired by the structured models of programming. In short, many application developers write in the relational database exactly like in the user interface. The other style of programming is holistic, data set oriented, and coded mainly in SQL. This is the style of the database developer.

The set based and holistic style of development is not promoted enough in universities, and many application developers are not fully aware of it. There are many performance issues all over the world in relational databases due to the use of the atomic and inappropriate style of programming. This book compares the two styles, and promotes the holistic style of development as the most suitable one. Examples are given to demonstrate the superiority of a set-based and holistic approach.
  • Compares the two styles of development
  • Shows the performance advantages of set-based development
  • Solves example problems using both approaches
Who This Book Is For

Two Styles of Database Development is aimed at application developers willing to adapt their programming styles in return for better-performing applications. It’s for students and new developers wanting to position themselves as having database expertise and build a reputation for developing highly-performant database applications. 
About the Author xiii
About the Technical Reviewer xv
Introduction xvii
Chapter 1 The Concept of Style
1(16)
Style of Development Is Dynamic
1(4)
SQL Requires Its Own Style
2(1)
Style and Quality
2(1)
A Programmer's Own Style
3(1)
Common Styles of Development
3(1)
Multitasking
4(1)
Team Organization
4(1)
The Visual Experience
5(1)
Common Models in Programming
5(3)
Object-Oriented Programming
6(1)
Structured Programming
6(1)
An Alternate Model?
7(1)
Can One Model Fit All?
7(1)
Starting with Table Design
8(4)
The Table as an Entity
8(1)
The Table As A Sum of Columns
9(1)
Database Constraints
9(2)
What Developers Must Know
11(1)
Let's Begin Coding
12(3)
Revisiting the Example
13(1)
Good Design May Be Wrongly Implemented
14(1)
Are You Ready for SQL?
15(2)
Chapter 2 SQL: Beauty and the Beast
17(14)
Can a Query Language Be So Important?
17(2)
Databases Require a Language
17(1)
SQL Is a Useful Language
18(1)
Programmers Must Adapt
18(1)
A Different Style Is Needed
19(1)
Understanding What SQL Is and Is Not
19(5)
SQL Is Not Classical Programming
19(1)
SQL Is About Querying
20(1)
Components of the SQL Language
21(1)
Queries and Clauses
22(1)
Inserting, Updating, and Deleting
23(1)
What About Programming?
24(2)
The Advantage of a Standard
26(2)
Programming Is a Practical Activity
26(1)
Is Database Programming Special?
27(1)
The SQL Shop Metaphor
28(1)
An Example of Bad Practice
29(2)
Chapter 3 A Holistic Vision of the Data
31(12)
The Concept of the Data Set
31(2)
The Importance of the Data Set
31(1)
SQL and the Data Set
32(1)
A Mix of Art and Science
32(1)
SQL and Portability
33(2)
Operating on Data Sets
33(1)
Two Approaches
33(1)
Data Sets as Atomic Units
34(1)
Like a Chameleon
34(1)
Thinking in Data Sets
35(1)
Take Style Seriously
35(3)
Understanding the Data Set
36(1)
The Importance of Style
36(1)
Programming as a Distinct Path
37(1)
Promoting the Holistic Style
37(1)
The Benefits
38(1)
Be Independent
38(5)
Visual vs. SQL Development
39(1)
Choosing a Tool or a Language
40(1)
Use SQL
41(2)
Chapter 4 Data by Set or by Row?
43(10)
Choosing the Level of Detail
44(1)
Working Atomically
44(1)
Row-by-Row Performance
45(2)
Writing Out of Habit
45(1)
Blocked into Poor Performance
46(1)
Performance Relies on a Holistic Style
46(1)
Querying... All the Time!
47(2)
What Do Programmers Do?
47(2)
How Do Programmers Do It?
49(1)
Revisiting the SQL Shop
49(1)
The Use of Scalar Functions
50(1)
Set-Based Debugging Is Simpler
51(1)
Your Role as a Database Developer
52(1)
Practice Time!
52(1)
Chapter 5 Data Transfer Paradigm
53(28)
About the Examples
53(1)
Format of the Examples
54(1)
Example 1 A Full Data Transfer Between Two Systems
54(16)
Business and Technical Description
55(1)
Prerequisites
55(4)
Sample of the Data
59(1)
An Example Insert Script
60(1)
Filtering for English and French
61(8)
Try It on Your Own
69(1)
Some Conclusions
69(1)
Example 2 Incrementally Update a Target
70(11)
Changes to the Source
70(1)
The Atomic Approach
71(5)
The Holistic Solution
76(5)
Chapter 6 The Challenge of Scalar Functions
81(22)
Cursors Have Their Place
81(1)
The Lure of Functions
82(1)
Divide and Conquer
82(1)
Example 3 Filtered Full Data Transfer
83(11)
The Atomic Solutions
84(7)
The Holistic Solutions
91(3)
Example 4 A Simple Query
94(9)
New Example Set
94(2)
Business Requirement
96(1)
The Atomic Solutions
97(2)
A Mixed Approach
99(1)
The Holistic Solutions
100(3)
Chapter 7 Writing SQL vs. Writing Procedurally
103(24)
An Example of an Update
103(5)
An Atomic Solution
104(2)
A Holistic Solution
106(2)
The Power of a Union
108(4)
Taking a SQL-Based Approach
108(1)
A Specific Example
108(1)
Union vs. if-else
109(3)
Write Accurate Code First
112(1)
Embedded SQL vs. Dynamic SQL
112(7)
The Normal Approach
113(1)
Uncertainty at Runtime
113(1)
The Use of SQL Generators
113(1)
An Example
114(2)
The Explanation
116(3)
Other Holistic Solutions
119(8)
Temporary Tables
120(1)
Table Functions
120(1)
One Last Atomic Example
121(2)
The Holistic Solution
123(1)
The Atomic Solution in SQL Server
124(1)
The Holistic Approach in SQL Server
125(2)
Chapter 8 Row Triggers and the Need for Atomic Solutions
127(10)
The Use of Row Triggers
127(5)
The Seduction
127(1)
The Trap of Row Triggers
128(1)
Some Example Triggers
128(1)
A Revised Solution
129(1)
The Disaster
130(2)
The Necessity of the Atomic Approach
132(5)
Analyzing the Example
132(3)
Reviewing the Solution
135(1)
Wrap-Up on Atomic Operations
136(1)
Chapter 9 Final Reflections and Thoughts
137(10)
The Principle of Division
137(1)
The Concept of a SQL Template
138(1)
Writing Horizontally vs. Vertically
139(1)
My Reason Against Tools
140(1)
Specific Software Applications
141(1)
SQL Itself Can Be Improved
142(1)
Performance, Oh Performance!
143(1)
Just the First Step
144(1)
Pure SQL is the Way
145(2)
Index 147
Stefan Ardeleanu was born in Bucharest, Romania in 1967. He graduated Math and Philosophy, and he was a math teacher for 10 years. Then he began a career in software development. He felt attracted by databases from the beginning, so his entire career in software industry is related to databases, and especially to developing applications that run on them. Stefan has many years experience in systems such as Oracle, SQL Server, DB2, and PostgreSQL. He has experience in OLTP and data warehousing, and with replication systems. Stefan is a passionate SQL guy, a database trainer, and he has delivered courses on Oracle products as an Oracle partner, especially database development courses and business intelligence courses. Stefan has published works in both Romanian and English. 
Lisainfo e-raamatute kohta Lisainfo e-raamatute kohta
Püsilink: https://www.kriso.ee/db/97814842208012e.html
Märksõnad: