Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Minimizing Table Sizes
Message
De
27/08/2007 08:36:04
Suhas Hegde
Dental Surgeon
Sirsi, Inde
 
 
À
26/08/2007 16:26:48
Randy Wessels
Screentek Business Solutions, Llc.
Phoenix, Arizona, États-Unis
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:
Vista
Network:
Windows 2003 Server
Database:
Visual FoxPro
Divers
Thread ID:
01250525
Message ID:
01250613
Vues:
9
>I support an application that is multi-user and designed fairly poorly. Not only are the detail tables populated with a ton of data that can be access from other tables, but the app is installed from the server with a link at each desktop. So as tables are needed, they are opened up over a network share. As these files get over 10 megs in size, performance is seriously degraded. I don't have the time to re-engineer the whole app, but I do want to try to reduce the physical size of the files as much as I can.
>
>I have started by dropping fields in the detail that I can join from other tables. I am reducing the size of text files where I don't need them to be as large. I have a few questions. If a field does not contain any data, does it still take up the same amount of size as if it did just based on the definition of the table? I have an item description field that can be overridden at the time that item is used on an order. The application stores that field in the table regardless of whether or not it is overridden. I can certainly change the app to only store the ones that are overridden, but does that get me anywhere? Also, I have numeric fields that are 12,2 that probably only need to be 9,2. Will that save any space?
>
>Thanks,
>
>Randy


hi,
Are You worring abt Speed on Load or On execution?

I was bitten one and even now and finding ways to load the whole table into memory

Try with a simple scan ... endscan at load of the tables so that the whole table gets cached into memory only if the clients have enough memory. Loading might be a tad slower but the result output might be just fast enough.

If there is less ram on the clients even with scan ... endscan (the fastest way i found to load a table in memory) the cached pages wuould be retired and cache cleared and would make no difference. But it is worth a try to see if it makes any difference.

suhashegde
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform