Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Rushmore optimization - index composed of 2 fields
Message
De
07/01/2009 09:07:23
 
 
À
07/01/2009 06:14:05
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Divers
Thread ID:
01371601
Message ID:
01371666
Vues:
27
Additionally, the indexed expression must be on the left.

LNAME + FNAME = "Smith" will be optimized but "Smith" = LNAME + FNAME will not be optimized.

>In order to get rushmore optimisation, the index must match exactly the expression in the where clause. In your case, and in general, I suggest having separate index tags instead or in addition to the two field index.
>
>And by the way, Set enginebehavior has nothing to do with rushmore. ALWAYS use Set enginebehavior 90 in production, other values must ONLY be used as "band aid" until you have fixed your select statements.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform