How can I keep to DB's in sync

Using Sequel Server or MSDE

[Red_Eye]

We are developing a web based service. With ASP.Net and a Sequel Server behind it (using MSDE for initial Development). As part of the service we need to offer a redundant backup server that would be switched to in the unlikely event of the main server going down.

The problem is how do we keep the databases on both machines up to date. We have several ideas, but no clear direction to take.

Any suggestions?

[webdevsf]

The optimal solution is to use clustering, which provides the most uptime. But that is expensive and difficult to setup.

The cheapest solution is to use log shipping (available with Sql Svr 2k), which sends the transaction logs to another warm server, and will lag your production server by a few minutes/hours.

Finally, you can use replication, which I personally don't like that much because it junks up your server with lots of GUIDs.

[txbakers]

If you set up a RAID 5 system on your server you can write to two hard drives simultaneously. If one crashes, the other takes over immediately.

[Red_Eye]

Thanks for your replies. We will be using a raid array on the main server which solves a failed harddisk problems. However we are keen have the backup on another PC in another location. The main reason for this is to protect against loss of internet connection, fire etc.

I like the sound of clustering I think that I understand what it is. Could you point me in the direction of more information on this topic.

Thanks in advance for your help