ACM Home Page
Please provide us with feedback. Feedback
Robustness in automatic physical database design
Full text PdfPdf (579 KB)
Source ACM International Conference Proceeding Series; Vol. 261 archive
Proceedings of the 11th international conference on Extending database technology: Advances in database technology table of contents
Nantes, France
SESSION: Research sessions: Physical design table of contents
Pages 145-156  
Year of Publication: 2008
ISBN:978-1-59593-926-5
Authors
Kareem El Gebaly  Ericsson
Ashraf Aboulnaga  University of Waterloo
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 8,   Downloads (12 Months): 69,   Citation Count: 0
Additional Information:

abstract   references   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1353343.1353365
What is a DOI?

ABSTRACT

Automatic physical database design tools rely on "what-if" interfaces to the query optimizer to estimate the execution time of the training query workload under different candidate physical designs. The tools use these what-if interfaces to recommend physical designs that minimize the estimated execution time of the input training workload. In this paper, we argue that minimizing estimated execution time alone can lead to designs with inherent problems. In particular, if the optimizer makes an error in estimating the execution time of some workload queries, then the recommended physical design may actually harm the workload instead of benefiting it. In this sense, the physical design is risky. Moreover, if the production queries are slightly different from the training queries, the recommended physical design may not benefit them at all. In this sense, the physical design is not general. We define Risk and Generality as two new metrics to evaluate the quality of a proposed physical database design, and we show one way of extending the objective function being optimized by a generic physical design advisor to take these measures into account. We have implemented a physical design advisor in PostgreSQL, and we use it to experimentally demonstrate the usefulness of our approach. We show that our two new metrics result in physical designs that are more robust, which means that the user can implement them with a higher degree of confidence. This is particularly important as we move towards truly zero-administration database systems in which there is not the possibility for a DBA to vet the recommendations of the physical design tool before applying them.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
PostgreSQL. http://www.postgresql.org.
2
 
3
 
4
S. Agrawal, S. Chaudhuri, L. Kollàr, A. P. Marathe, V. R. Narasayya, and M. Syamala. Database tuning advisor for Microsoft SQL Server 2005. In Proc. VLDB, 2004.
 
5
6
7
8
9
 
10
N. Bruno and S. Chaudhuri. Efficient creation of statistics over query expressions. In Proc. ICDE, 2003.
11
12
 
13
N. Bruno and S. Chaudhuri. Physical design refinement: The "merge-reduce" approach. In Proc. EDBT, 2006.
 
14
 
15
N. Bruno and S. Chaudhuri. An online approach to physical design tuning. In Proc. ICDE, 2007.
16
17
18
 
19
 
20
 
21
K. El Gebaly. Robustness in automatic physical database design. Master's thesis, University of Waterloo, 2007. Also available as University of Waterloo Computer Science Technical Report CS-2007-29.
 
22
 
23
 
24
Transaction Processing Performance Council. TPC-H, the Ad-hoc Decision Support Benchmark. http://www.tpc.org.
 
25
 
26
Collaborative Colleagues:
Kareem El Gebaly: colleagues
Ashraf Aboulnaga: colleagues