Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > microsoft.public.sqlserver.server > #18800
| X-Received | by 10.107.150.74 with SMTP id y71mr717312iod.94.1503415894120; Tue, 22 Aug 2017 08:31:34 -0700 (PDT) |
|---|---|
| X-Received | by 10.31.141.142 with SMTP id p136mr7869vkd.21.1503415894039; Tue, 22 Aug 2017 08:31:34 -0700 (PDT) |
| Path | csiph.com!xmission!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!x187no773259ite.0!news-out.google.com!a17ni4867qth.1!nntp.google.com!v29no2923686qtv.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail |
| Newsgroups | microsoft.public.sqlserver.server |
| Date | Tue, 22 Aug 2017 08:31:33 -0700 (PDT) |
| In-Reply-To | <1ec58b2f-46c0-41d2-906e-391f6b435722@googlegroups.com> |
| Complaints-To | groups-abuse@google.com |
| Injection-Info | glegroupsg2000goo.googlegroups.com; posting-host=49.206.117.18; posting-account=bMmwHQoAAABIEfLueE9Xq_508m77fsVs |
| NNTP-Posting-Host | 49.206.117.18 |
| References | <1ec58b2f-46c0-41d2-906e-391f6b435722@googlegroups.com> |
| User-Agent | G2/1.0 |
| MIME-Version | 1.0 |
| Message-ID | <7fc1621d-cb60-4b19-a0ae-bdc2a9e082a6@googlegroups.com> (permalink) |
| Subject | Re: Always On Availability between 2 separate SQL Clusters |
| From | call2sqldba@gmail.com |
| Injection-Date | Tue, 22 Aug 2017 15:31:34 +0000 |
| Content-Type | text/plain; charset="UTF-8" |
| Content-Transfer-Encoding | quoted-printable |
| Lines | 15 |
| Xref | csiph.com microsoft.public.sqlserver.server:18800 |
Show key headers only | View raw
On Saturday, September 12, 2015 at 12:00:07 AM UTC+5:30, Query Builder wrote: > I have an active passive cluster on my primary Data center in NY and have a DR Active / passive SQL Cluster in TX. > Both clusters host an active / passive SQL instance. Lets call it SQLNY(Primary) and SQLTX (DR). I want to enable always On Availability group within the two SQL Instances SQLNY and SQLTX. The listener will be SQLAG. This will be able to run under any of the 4 nodes (2 in NY and 2 in TX based on status). > > Is there a practical way to implement this? This will not only give me instant fail over within the NY (Primary) but also give me the flexibility to fail over to TX. > > I am using SQL 2014 Enterprise Edition on both clusters. Any help will be much appreciated..
Back to microsoft.public.sqlserver.server | Previous | Next — Previous in thread | Next in thread | Find similar
Always On Availability between 2 separate SQL Clusters Query Builder <querybuilder@gmail.com> - 2015-09-11 11:29 -0700 Re: Always On Availability between 2 separate SQL Clusters call2sqldba@gmail.com - 2017-08-22 08:31 -0700 Re: Always On Availability between 2 separate SQL Clusters call2sqldba@gmail.com - 2017-08-22 08:54 -0700
csiph-web