Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 11 to 11 of 11 total |
Evaluating DBIsam - Performance testing |
Mon, Jan 16 2006 1:19 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Mark,
<< Ensured cas-ins set to false on all indexes. Changed where clause to Upper(surname) = Upper('SMITH') >> Actually, you don't need the UPPER() function around both sides if the available index is case-sensitive: surname = 'SMITH' My comment was meant to let you know that if you *did* have a case-insensitive index, then you would need to use the UPPER() function around both sides in order to ensure that it is optimized. Also, in case you didn't know, you can set the TDBISAMQuery.GeneratePlan property to True in order to have DBISAM populate the TDBISAMQuery.Plan property when you execute the query. It will show you whether the query's WHERE clause is optimized or not. -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Friday, April 26, 2024 at 06:09 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |