Monday, February 27, 2012

Hot-standby SQL Server Using Alias Name?

I want to have a hot standby SQL server for my clients. My idea is to install
SQL on two separate machines, SRVA and SRVB, and configure continuous merge
replication between them. Client machines would connect to an alias name,
SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon failure, DNS
would be changed to point to SRVB. Could something like this work? If so, how
would one start to implement it?
Maybe a shorther question would be, is it possible for clients to connect to a
SQL server alias name (not a named instance) instead of the actual machine
name of the server?
--Eric RobinsonThis is a multi-part message in MIME format.
--=_NextPart_000_0370_01C3A9EA.14018070
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
Consider using a clustered installation of SQL Server. It has automatic
failover and requires no human intervention.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Eric Robinson" <eric@._nospam_nvipa.com> wrote in message
news:CFN379384331352315@.news.microsoft.com...
I want to have a hot standby SQL server for my clients. My idea is to
install
SQL on two separate machines, SRVA and SRVB, and configure continuous merge
replication between them. Client machines would connect to an alias name,
SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon failure,
DNS
would be changed to point to SRVB. Could something like this work? If so,
how
would one start to implement it?
Maybe a shorther question would be, is it possible for clients to connect to
a
SQL server alias name (not a named instance) instead of the actual machine
name of the server?
--Eric Robinson
--=_NextPart_000_0370_01C3A9EA.14018070
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Consider using a clustered =installation of SQL Server. It has automatic failover and requires no human intervention.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Eric Robinson" =wrote in message news:CFN3793843313523=15@.news.microsoft.com...I want to have a hot standby SQL server for my clients. My idea is to =install SQL on two separate machines, SRVA and SRVB, and configure =continuous merge replication between them. Client machines would connect to an alias =name, SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon =failure, DNS would be changed to point to SRVB. Could something like this =work? If so, how would one start to implement it?Maybe a shorther =question would be, is it possible for clients to connect to a SQL server =alias name (not a named instance) instead of the actual machine name of the server?--Eric Robinson

--=_NextPart_000_0370_01C3A9EA.14018070--

No comments:

Post a Comment