You are here

high availability

SQL Server Maintenance Plan Backups Failing On Secondary Replica in High Availability Environment

When a High Availability (HA) environment failed over, on the node that became Secondary, the backup jobs did not gracefully handle the change. The Maintenance Plans are supposed to intelligently determine whether each database is Primary or Secondary in an HA environment, and skip the backup if it is not Primary.  This check actually fails (practically speaking) if you have "Verify backup integrity" checked.

T-SQL - Get Listener Name on AlwaysOn Cluster

When using AlwaysOn, you must connect using your listener name, not your node name.  If you connect with the node name, it will only work until there is a failover, which would defeat the purpose of your High Availability setup, right?

CAPTCHA
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
9 + 10 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer