Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
High-availability technologies mask the effects of hardware or software failure, so that perceived downtime for users and applications is minimized.
0
votes
Accepted
AlwaysOn High Availability - not always kicking in
A deeper dive into the MS's documentation helped us discover the Flexible Automatic Failover Policy (https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/flexible-automati …
0
votes
1
answer
638
views
AlwaysOn High Availability - not always kicking in
We currently have a set up of two nodes A and B with AlwaysOn High Availability.
When restarting node A, we can connect with the listener name 'xyz' to our SQL Server instance. In this scenario, B wil …