What is the best failover I can do with 2x WS2k8 standard and 2x SQL server 2k8?

[brxndxn]

I want to create a new centralized database that will not hold a lot of information (<4gb total), but will be absolutely mission critical. I am not afraid of any new technologies or hardware.

I was hoping to just use database mirroring with SQL Server 2008, but it looks like Microsoft did the following to screw me:
- it requires Windows Server 2008 Enterprise edition (which costs ~$2500 instead of $~700)
- database mirroring is being phased out in future SQL editions in favor of 'always on' availability options

When I originally talked to the Microsoft representative, I was told I could do some sort of 'hot standby' option in SQL server 2008 standard on top of Windows Server 2008 standard. Now, I cannot find any information about this.

I guess another, but crappy, option is to just write a procedure that automatically mirrors changes on a per table basis and configure clients to access either server.

My client wants the ability to unplug either server (simulating a total hardware failure) and have the clients still have acess to the same tables.

Any suggestions?

 

[pauldun170]

What about log shipping?
http://msdn.microsoft.com/en-us/library/ms187103.aspx

As for Database mirroring, Standard supports it but only in synchronous mode.

 

[AFurryReptile]

What about DFS Replication? Not sure how well it works with SQL, but it's worked great for keeping our mission-critical data mirrored between servers. In the event of a failure, DFS Namespace automatically fails over to the second (or more) servers. The users don't notice a thing.

Just really read the technet first, and set it up properly. The potential to have a lot of problems is there if you mess up the config.

 

[Lifted]

AFAIK pulling the plug without downtime would require clustering, and clustering always requires Windows Enterprise. I don't think that has ever not been the case.

Sell them on a SQL 2012 DAG. DAG's work great with Exchange.