I have one table, and indexes are created for all the columns still. I'm getting table access full for the same table, please tell me how to avoid TAF in Oracle database.
Full table scans are not necessarily bad. If the optimizer thinks that doing a full scan is more efficient than using some other access path, it will do a full scan, and that is good.
We would need more information in order to know if a full table scan sounds like a good option in your specific case.
At a minimum, we would need to know the table definition, the existence of indexes, the number of rows in the table, the number of distinct values in the columns you are using to filter, and of course, your query and an execution plan.
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!
Discuss This Question: 1 Reply
We would need more information in order to know if a full table scan sounds like a good option in your specific case.
At a minimum, we would need to know the table definition, the existence of indexes, the number of rows in the table, the number of distinct values in the columns you are using to filter, and of course, your query and an execution plan.
The database version is also important.