How to prevent Firebird from using an index in the query?


Although the query optimizer is doing its best to choose the appropriate indexes in queries, it may sometimes happen that you see an index in query plan that you think should not be used (because of low selectivity, etc.)

It might help to recalculate index statitics using SET STATISTICS command, but if you really just want to avoid using index, you can add +0 or ||'' to the integer or string column. Example:

SELECT * FROM EMPLOYEE where LAST_NAME = 'Nelson';
PLAN (EMPLOYEE INDEX (NAMEX))

To disable use of NAMEX index we use:

SELECT * FROM EMPLOYEE where LAST_NAME||'' = 'Nelson';
PLAN (EMPLOYEE NATURAL)

Here's an integer example also:

SELECT * FROM EMPLOYEE where EMP_NO > 2;
PLAN (EMPLOYEE INDEX (RDB$PRIMARY7))

SELECT * FROM EMPLOYEE where EMP_NO+0 > 2;
PLAN (EMPLOYEE NATURAL)

Another common practice is to add some expression that evaluates to false, for example 1 = 0. Example:

SELECT * FROM EMPLOYEE where EMP_NO > 2 OR 1 = 0;
PLAN (EMPLOYEE NATURAL)



Do you find this FAQ incorrect or incomplete? Please e-mail us what needs to be changed. To ensure quality, each change is checked by our editors (and often tested on live Firebird databases), before it enters the main FAQ database. If you desire so, the changes will be credited to your name. To learn more, visit our add content page.

If you are a commercial tool maker and your tool features a great way to handle the issue written about in this FAQ, please check out our advertisement page.



All contents are copyright © 2007-2017 FirebirdFAQ.org unless otherwise stated in the text.


Links   Firebird   News   FlameRobin   Home Inventory powered by FB  
Add content   Advertise   About  

Categories
 Newbies
 SQL
 Installation and setup
 Backup and restore
 Performance
 Security
 Connectivity and API
 HOWTOs
 Errors and error codes
 Miscellaneous