ACM Home Page
Please provide us with feedback. Feedback
Validating the Oracle SQL engine
Full text PdfPdf (202 KB)
Source International Conference on Management of Data archive
Proceedings of the Second International Workshop on Testing Database Systems table of contents
Providence, Rhode Island
SESSION: DBMS and SQL testing table of contents
Article No. 4  
Year of Publication: 2009
ISBN:978-1-60558-706-6
Authors
Allison Lee  Oracle USA, Redwood Shores, CA
Mohamed Zait  Oracle USA, Redwood Shores, CA
Thierry Cruanes  Oracle USA, Redwood Shores, CA
Rafi Ahmed  Oracle USA, Redwood Shores, CA
Yali Zhu  Oracle USA, Redwood Shores, CA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 17,   Downloads (12 Months): 32,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1594156.1594161
What is a DOI?

ABSTRACT

The query engine is the component inside a database system that is responsible for the compilation and execution of every SQL statement submitted by a database user or application. One of the most important steps of query compilation is query optimization. The goal of query optimization is to find the best execution plan based on metadata and statistics about the objects related to the tables referenced in the statement. There are two distinct kinds of query optimization: logical and physical. During logical optimization the structures of the query are changed by applying transformations such as view merging, subquery unnesting, etc. Physical optimization considers the physical properties of the tables (disk layout, access methods, size) and properties of the relational algebra operations (commuting joins) to find the best execution plan for a given query shape as presented by the logical optimization.

The changes made to the SQL statement during query optimization can be temporary (to cost a particular optimization) or permanent (after an optimization is considered final). In this paper we discuss the quality problems that occur during the manipulation of the query structures that take place during query compilation with a focus on query optimization. We propose (1) a method to validate query structure change; (2) a method to validate plans that are discarded during query optimization but that may be picked under different circumstances.


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
Oracle 11g Documentation http://ww.oracle.com/pls/db111/homepage
 
2
 
3
4
 
5
 
6
Giakoumakis, L. and Galindo-Legaria, C. Testing SQL Server's Query Optimizer: Challenges, Techniques and Experiences. IEEE Data Engineering Bulletin, 31, 1 (March 2008), 37--44
 
7
Liskov, B. and Guttag, J. Program Development in Java. Addison-Wesley, Reading MA, 2000.
8
 
9
Oracle 11g Release 1 Database Performance Tuning Guide http://www.oracle.com/pls/db111/to_toc?pathname=server.111/b28274/toc.htm
 
10
11
 
12

Collaborative Colleagues:
Allison Lee: colleagues
Mohamed Zait: colleagues
Thierry Cruanes: colleagues
Rafi Ahmed: colleagues
Yali Zhu: colleagues