Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Database update, best practices
Message
De
25/01/2002 10:03:09
Carol Dewar
Magram Computer Services Llc
Saugerties, New York, États-Unis
 
 
À
25/01/2002 06:20:29
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00610172
Message ID:
00610455
Vues:
25
Hmmm,
So we can, after copying everything to the backup directory:
Replace all of the client's database/tables with empty, updated database/tables from the library.
Run the generate client dictionary and structure compare code to log all the changes.
DOS COPY tables, for no hits. APPEND FROM (and initialize if needed) for any hits in a table.

We have no Database considerations.
This is like my 1st senario only less complex.
Have you automated this? done this remotely? Any "Lights out" problems? considerations?
Thanks,
Carol Dewar

>Well, what I do is keep an empty structure of the database (+ tables), copy everything to a temp directory, and issue APPEND FROM for each table. Additional considerations: 1) in the case of RI, the parent table has to be copied before the child tables. Otherwise (if the third RI column is "R") you get "trigger failed". 2) to speed things up, I do a detailed comparison of table structures. If the structures are identical, the table is copied with the COPY command.
>
>HTH, Hilmar.
Carol Dewar
Magram Computer Services LLC
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform