Proceedings of the 1979 ACM SIGMOD International Conference on Management of Data - SIGMOD '79 1979
DOI: 10.1145/582096.582099
|View full text |Cite
|
Sign up to set email alerts
|

Access path selection in a relational database management system

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
485
0
8

Year Published

1996
1996
2013
2013

Publication Types

Select...
5
4
1

Relationship

0
10

Authors

Journals

citations
Cited by 343 publications
(494 citation statements)
references
References 0 publications
1
485
0
8
Order By: Relevance
“…The potential to generate such different ordered tuple streams leads to different, and sometimes conflicting sandwiching opportunities higher up in the plan. Due to space restrictions, the question how to choose the best orderings is beyond the scope of this paper, but we can note here that our solution seamlessly fits into the well known concept of interesting order optimization [13], and on which we will report in a subsequent paper. …”
Section: Query Optimizationmentioning
confidence: 98%
“…The potential to generate such different ordered tuple streams leads to different, and sometimes conflicting sandwiching opportunities higher up in the plan. Due to space restrictions, the question how to choose the best orderings is beyond the scope of this paper, but we can note here that our solution seamlessly fits into the well known concept of interesting order optimization [13], and on which we will report in a subsequent paper. …”
Section: Query Optimizationmentioning
confidence: 98%
“…The order is determined by "access path selection", a standard optimization from the database literature [14], to estimate the cheapest way to join the predicates together. The overall process involves a number of steps.…”
Section: Implementation and Optimizationmentioning
confidence: 99%
“…The execution cost is largely dependent upon the number of rows (the row cardinality) that will be processed by each operator in the QEP, so the optimizer first estimates this incrementally as each predicate is applied by multiplying the base table's row cardinality by a filter factor or selectivity for each predicate in the Query [5,6,7,8].…”
Section: Related Workmentioning
confidence: 99%