Can anyone clarify exactly what MS offers in their clustering in relation to SQL. For example, I know you can Replicate SQL and you can cluster it. When I think of cluster I think of a shared disk space that both servers access, when one server fails the other takes over looking at the same physical data location. When I think of replication I think of two servers with separate disks replicating data across servers and disk space. Does MS offer the option to replicate to two separate SQL servers with separate disk storage AND failover automatically, i.e. server 2 takes on the network identity of server 1 automatically? I understand that Double Take does this, I am just trying to clarify whether MS offers the same features or not. thanks Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd D8453 Scottsdale, AZ 85262 (602) 432-8649 www.thinclient.net steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Evan Mann Sent: Tuesday, August 16, 2005 10:07 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Slightly OT: SQL Redundancy No I did not. Was after failover/high availability more so than clustering for more performance. Ended up just adding 2 additional SQL servers when things started to getting heavy, of course this means even more hardware sitting around idle and even more licenses to buy, but since the servers are all spec'd the same, it gives me a lot of spare hardware to play with in the event of failures. _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk Sent: Tuesday, August 16, 2005 1:04 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Slightly OT: SQL Redundancy Thanks, did you also evaluate the GeoCluster product as well? Joe _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Evan Mann Sent: Tuesday, August 16, 2005 8:56 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Slightly OT: SQL Redundancy Double-Take. I successfully replicate with it, AND have successfully migrated to a newer SQL server using it. I tried to do an automatic failover, but it didn't work properly because the Double-Take service wasn't running as a Domain Admin, so it couldn't rename the computers in AD properly. Aside from that, the database aspect of it was 100% flawless. It does bit-by-bit replication of files, so as long as you replicate all your DBs, master, etc., it will work great. _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk Sent: Tuesday, August 16, 2005 11:55 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Slightly OT: SQL Redundancy Hello, What a success (or failure) has the group encountered in making SQL servers Highly Available? Either through clustering (Microsoft or third-party) or replicated partners. We are looking to move the Citrix DataStore and a few application databases to a HA solution, while minimizing the impact to farm in event an HA partner goes down. Joe