Redundancy

Hi All,

After some feedback from some of you who might have done something similar:

We are going to be having 3 SQL servers (running SQL Std licence).
2 Are live
1 is a hot swap in the event that we have a total loss of either of the SQL boxes.
Basically what I am wanting to do, is have the hot swap being updated periodically so that the databases are being replicated on this box, so that if the live one fell over, we could very quickly get the hot swap into take over.

Can anyone offer any perspectives on the best method of attack for this?

Thanks in advance for your thoughts.

CheersTry to implement your own log shipping by referring to this article http://www.sql-server-performance.com/sql_server_log_shipping.asp and this http://support.microsoft.com/default.aspx?scid=kb;en-us;314515 KBA for FAQs about LS.|||Brilliant - thanks this is exactly what I was after.

Thanks!|||This is only a thought, but you could also do transactional replication to the third box. If one of the two other servers dies, all you need to do is drop all of the replication and rename the third box to take the place of the downed server.

This buys two advantages from my perspective... First, it gives you a "live" set of data that you can query, etc. to take load off of your production database(s). As a nice side benefit, it gives you literally "up to the minute" data, there is no loss due to log shipping delays if you ever need to use it!

-PatP