Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
completely unoptimized filter? |
Wed, Oct 25 2006 4:51 AM | Permanent Link |
"Santy Concepción" | Hi!
I have been testing filters optimizations of my application, but I don't understand why they are unoptimized... I have a table with some secondary indexes (no primary index). It has a very simple filter: "NUMBER >= 3" Field "NUMBER" is an Integer indexed field. I have tried the index with other fields of the same table, and all of them are unoptimized. Is it normal? Thanks! |
Wed, Oct 25 2006 6:19 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Santy,
<< I have a table with some secondary indexes (no primary index). It has a very simple filter: "NUMBER >= 3" Field "NUMBER" is an Integer indexed field. I have tried the index with other fields of the same table, and all of them are unoptimized. >> Try running them as a live query in the DBSYS utility, i.e. something like this: SELECT * FROM MyTable WHERE NUMBER >= 3 and make sure to check the Live Result Set and Generate Plan check boxes. You can then look at the Plan tab to see exactly what DBISAM is doing with the filter condition in terms of using indexes, etc. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 5, 2024 at 07:30 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |