Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Primary key can't be optimized?
Message
De
18/02/2001 21:59:01
 
 
À
18/02/2001 08:31:02
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00477099
Message ID:
00477169
Vues:
25
>Hi,
> I am having Customer ID as primary key for my customer table. I found that, it is slow for searching a customer record using either LOCATE FOR or SQL-SELECT. Therefore, I set Customer ID as regular key in table as well. It really optimized the query. The speed of search is just like "light of speed".
>
>Why could it happen?
>

Did the primary key have a FOR clause in it? If so, Rushmore won't use the index for optimization. If you removed the FOR clause when coverting to a regular index, that's probably the reason.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform