How do I tune a SQL statement when the Optimizer picks the wrong index?
Maria Colgan (SQLMaria)
View ChannelAbout
Welcome to my YouTube channel, where I share information on Oracle Database features and functionality to demonstrates how you can revolutionize Data Management by adopting Transformational Technologies! This YouTube channel is used in conjunction with my blog https://sqlmaria.com, which has all of the code examples used in the videos in an easy to cut-and-paste format. All content Copyright © 2021 Oracle and/or its affiliates. Oracle is a registered trademark of Oracle and/or its affiliates. All rights reserved. Other names may be registered trademarks of their respective owners. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the “Materials”). The Materials are provided “as is” without any warranty of any kind, either express or implied, including without limitation warranties or merchantability, fitness for a particular purpose, and non-infringement.
Latest Posts
No results found. Try different keywords.
Video Description
Understanding why the Optimizer makes a decision and providing the necessary information and access methods to allow the Optimizer to pick the plan you want by default can be challenging. But don't give in to the overwhelming temptation to use a hint to brut force the plan you want. In this short video, I explain why the Optimizer didn't choose the index folks were expecting, how to identify these types of problems and provide you with the solution. Hopefully, you will be able to apply the lessons shown in this video to your SQL Tuning tasks on your own systems!
SQL Tuning Tools You Can't Miss
AI-recommended products based on this video
