Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Avoiding Duplicate Records
Message
De
12/08/2008 21:38:09
 
 
À
12/08/2008 07:13:53
Jon Neale
Bond International Software
Wootton Bassett, Royaume Uni
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Import/Export
Versions des environnements
SQL Server:
SQL Server 2000
Divers
Thread ID:
01337412
Message ID:
01338489
Vues:
13
Jon:

Add/Edit/Delete of data are all done on the primary server only - then transfered to the secondary server.

Again thank you.

Mal

>Just a clarification, is anybody on the second server actually adding in new records through the VFP application or does this just happen from the primary server.
>
>
>>Jon:
>>
>>Yes, I could do a backup and restore, however, I found that when you do this, you have to reset the privileges and it takes a while. I'd rather not do this everytime an update is performed - sometimes it's only about a 30 record update. Am I wrong here?
>>
>>Thanks
>>
>>Mal
>>
>>>Hi,
>>>
>>>What are you using the second database for? Could you not just back up and restore the primary server database to the secondary database? If you need anything more than this then I think you should probably have a look at replication.
>>>
>>>Jon
>>>
>>>
>>>>Hi:
>>>>
>>>>I have 2 locations each with a SQL Server machine. One machine is alwasy updated. I use EXPORT from the updated machine then IMPORT into the other machin to keep the machines the same. This has been working out, but recently I've been getting duplicate recrods. How do I implement an IMPORT and elimnate/ignore dulicate records. Is there a way to tell SQL Server's Import to ignore records already in the table?
>>>>
>>>>TIA
>>>>
>>>>Mal
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform