Jon:

Sounds very promissing. I'll give it a go.

Thank you.

Mal

>Is it just the logins that fall out of sinc?
>
>You should look at sp_change_users_login which can be used to realign the user logins when restoring a database to a different server. You could include this into a script to restore the database and set it up as a job to run every night or however often.
>
>Jon
>
>>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