Hi everyone,

I am currently a data warehouse DBA that is part of a group that has been charged with setting up our Intranet SQL Server fail over scheme. Currently, we have a three-tier Internet setup. Two F5 load balancing/fail over servers are attached to three application servers that are attached to two SQL Server data servers.

The first scenario we are looking at is to make one of the data servers primary and the second a standby. The OTLP tables would be kept in sync using Transactional Replication and the Lookup tables (loaded nightly), would be kept in sync using Snapshot Replication. In the event that the primary SQL Server fails, the F5 unit would switch the standby SQL Server to primary.

The second scenario would be to set up an Active/Active Clustering scheme as described in the SQL Server 2000 Administration book.

The first scenario would be the quickest and least costly solution because we have everything needed to set it up. For the Second, we would have to upgrade versions of SQL Server and add network connections.

As part of my research, I would appreciate hearing how your shop handled Internet fail over, as well as, comments about either of our two scenarios.

Thanks,
Don

Donald Graves
Unisys Corporation
Louisiana Medicaid MIS
8591 United Plaza Blvd., Ste 300
Baton Rouge, LA 70809
225-237-3389 phone
225-237-3373 fax
donald.[Email address protected]

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.




MS Sql Server LazyDBA home page