Abstract
As I mentioned at the beginning of Chapter 1, SQL is a declarative programming language. In theory, you just have to say what you want to have done and then something works out how to do it. In the case of an Oracle database, that “something” is the CBO, and it should devise an appropriate execution plan for you. In theory you shouldn’t have to worry about getting incorrect results and you shouldn’t have to worry about performance. Since you are reading this book you have almost certainly realized that life isn’t as simple as that and that you do, in fact, have to worry quite a bit. With the exception of bugs, the results of a correctly written SQL statement will be correct, but optimal performance, or even acceptable performance, is far from guaranteed, even from a bug-free database.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
It would have made more sense for more to suggest that direct sales have a sales representative and online sales do not. Unfortunately, the sample data doesn’t follow that rule!
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2014 Tony Hasler
About this chapter
Cite this chapter
Hasler, T. (2014). Why Do Things Go Wrong?. In: Expert Oracle SQL. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-5978-7_14
Download citation
DOI: https://doi.org/10.1007/978-1-4302-5978-7_14
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-5977-0
Online ISBN: 978-1-4302-5978-7
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books