Skip to Main Content
Automated Physical Database Design and Tuning
book

Automated Physical Database Design and Tuning

by Nicolas Bruno
February 2011
Intermediate to advanced content levelIntermediate to advanced
253 pages
8h 4m
English
CRC Press
Content preview from Automated Physical Database Design and Tuning
Constrained Physical Database Design 209
As an example, consider the following constraint:
ASSERT size(C) - size(COrig) 200M
In this situation, D(C, F) =↓ for any C because any sequence of transfor-
mations starting with C will result in a smaller configuration, and therefore
the value of F always decreases. Although the definition of D is precise, in
practice it might be unfeasible to evaluate D for arbitrary values of F.Ifwe
cannot prove that D(C, F) ∈{↑, , ↔} we return the unknown value ? ”. Op-
erationally, we evaluate D in a bottom-up manner. We first assign D values
for the primitive function calls:
D(C, size(C)) =↓
D(C, size(Tables[”R”])) =↔
D(C, cost(Q, C)) = if type(Q)isSELECT then else ?
and then propagate results through operators using
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

What Is Database Design, Anyway?

What Is Database Design, Anyway?

C.J. Date
Physical Database Design

Physical Database Design

Sam S. Lightstone, Toby J. Teorey, Tom Nadeau

Publisher Resources

ISBN: 9781439815670