AlwaysOn Professional
learn.microsoft.com/en-us/archive/blogs/alwaysonpro
Home of the Microsoft SQL Server AlwaysOn Support Team
DatabasesDistributed systems / cloudMicrosoft blogsMSDN archive
- Posts
- 56 from 28 Jun 2013 to 6 Feb 2018
- Posting
- archived, read-only
- Kind
- company blog
- Feed
- https://learn.microsoft.com/en-us/archive/blogs/alwaysonpro/feed.xml
2018 1
2017 6
- Analyze Network Latency Impact on Remote Availability Group Replica
- Availability Group Database Reports Not Synchronizing / Recovery Pending After Database Log File Inaccessible
- Avoid Availability Group Database Data Loss: Do not Deploy File Share Witness From DFS Namespace
- Troubleshooting Internal Load Balancer Listener Connectivity in Azure
- How to Apply Transaction Logs to Secondary When it is Far Behind
- Making Service Broker Application Highly Available With AlwaysOn
2016 9
- AlwaysOn Readable Secondaries Can Display Misleading Data & Log File Paths
- SQL Server 2016 AlwaysOn Availability Group Enhancements: Support for Encrypted Databases
- SQL Server 2016 AlwaysOn Availability Group Enhancements: Multiple Automatic Failover Targets
- SQL Server 2016 AlwaysOn Availability Group Enhancements: Load Balance Read-Only Routing
- SQL Server 2016 AlwaysOn Availability Group Enhancements: Initial Data Synchronization Without Database and Log Backup
- SQL Server 2016 AlwaysOn Availability Group Enhancements: Basic Availability Group on Standard Edition
- Improved AlwaysOn Availability Group Lease Timeout Diagnostics
- Troubleshooting Availability Group Listener in Azure
- Enhance AlwaysOn Failover Policy to Test SQL Server Database Data and Log Drives
2015 7
- Replication Agents fail to connect to listener in a multisite cluster
- Failing back from DR site after primary site is back online
- AlwaysOn Availability Group Listener Cannot be Created or Failed Over on Node if 'Primary DNS suffix' is not set
- AlwaysOn Availability Group Returns Failover Partner for Legacy Mirror Application Connectivity
- Recommendations for Index Maintenance with AlwaysOn Availability Groups
- How to add a TDE encrypted database to an Availability Group
- Troubleshooting REDO queue build-up (data latency issues) on AlwaysOn Readable Secondary Replicas using the WAIT_INFO Extended Event
2014 22
- Diagnose Unexpected Failover or Availability Group in RESOLVING State
- Large Transaction Interrupted by Failover, Secondary Database Reports REVERTING
- Troubleshooting the Add Azure Replica Wizard in SQL Server 2014
- Determine Availability Group Synchronization State, Minimize Data Loss When Quorum is Forced
- Enhance AlwaysOn Failover Policy to Test SQL Server Responsiveness
- Recommendations and Best Practices When Deploying SQL Server AlwaysOn Availability Groups in Microsoft Azure (IaaS)
- Connection Timeouts in Multi-subnet Availability Group
- IaaS with SQL AlwaysOn - Tuning Failover Cluster Network Thresholds
- Create Azure Listener fails with "Unable to save property changes for <cluster resource name> The parameter is incorrect"
- Use ReadIntent Routing with Azure AlwaysOn Availability Group Listener
- Create Listener Fails with Message 'The WSFC cluster could not bring the Network Name resource online'
- Manual Failover of Availability Group to Disaster Recovery site in Multi-Site Cluster
- SQL Server manages Preferred and Possible Owner Properties for AlwaysOn Availability Group/Role
- How to map logins or use contained SQL database user to connect to other replicas and map to availability databases
- Issue: Replica Unexpectedly Dropped in Availability Group
- Setting up Replication on a database that is part of an AlwaysOn Availability Group
- How to enable TDE Encryption on a database in an Availability Group
- Reducing Loss of Connectivity when Recreating an Availability Group
- Modifying AlwaysOn Read Only Routing Lists
- MSDTC Recommendations on SQL Failover Cluster
- Not-Supported: AGs With DTC/Cross-Database Transactions
- Maintenance Plan Does not Backup Database or Log of Database Defined in Availability Group
2013 11
- Create Availability Group Fails With Error 35250 'Failed to join the database'
- Recovery On Secondary Lagging – Shared Redo Target
- How It Works: SQL Server AlwaysOn Lease Timeout
- Configure Availability Group to Communicate on a Dedicated Network
- Create Availability Group Listener Fails with Message 19471, ‘The WSFC cluster could not bring the Network Name resource online’
- SQLPass 2013 Presentation "Enterprise High Availability with AlwaysOn Availability Groups [DBA-398-P]"
- Performing Transaction Log Backups using AlwaysOn Availability Group Read-Only Secondary Replicas - Part 1
- LooksAlive and IsAlive Implementation of Availability Groups failure_condition_level
- Connect to SQL Server Using Application Intent Read-Only
- End to End - Using a Listener to Connect to a Secondary Replica (Read-Only Routing)
- AlwaysOn Availability Groups Troubleshooting and Monitoring Guide