<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AlwaysOn AG on Rudi Bruchez</title><link>https://www.pachadata.com/en/tags/alwayson-ag/</link><description>Recent content in AlwaysOn AG on Rudi Bruchez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 28 Aug 2026 16:31:38 +0200</lastBuildDate><atom:link href="https://www.pachadata.com/en/tags/alwayson-ag/index.xml" rel="self" type="application/rss+xml"/><item><title>SQL Server Standard: understanding Basic Availability Groups (BAG)</title><link>https://www.pachadata.com/en/docs/howtos/hadr/bag/</link><pubDate>Tue, 27 Jan 2026 00:00:00 +0000</pubDate><guid>https://www.pachadata.com/en/docs/howtos/hadr/bag/</guid><description>&lt;div class="alert alert-success" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;TL;DR&lt;/div&gt;&#10;&lt;p&gt;&lt;strong&gt;Basic Availability Groups (BAG)&lt;/strong&gt; give SQL Server Standard edition users high availability similar to the Always On AG of the Enterprise edition, but with significant limitations:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;One group per instance.&lt;/li&gt;&#10;&lt;li&gt;One database per group.&lt;/li&gt;&#10;&lt;li&gt;No reads on the secondary replica.&lt;/li&gt;&#10;&lt;li&gt;No backups on the secondary.&lt;/li&gt;&#10;&lt;li&gt;Two nodes maximum, primary and secondary.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;For a long time, using &lt;strong&gt;Always On Availability Groups&lt;/strong&gt; required an Enterprise licence, leaving Standard edition users with &lt;em&gt;Database Mirroring&lt;/em&gt;. Since SQL Server 2016, Microsoft has offered &lt;strong&gt;Basic Availability Groups (BAG)&lt;/strong&gt; as the replacement for mirroring in the Standard edition.&lt;/p&gt;</description></item><item><title>Always On: mastering the timeouts</title><link>https://www.pachadata.com/en/docs/howtos/hadr/failovers/</link><pubDate>Tue, 27 Jan 2026 00:00:00 +0000</pubDate><guid>https://www.pachadata.com/en/docs/howtos/hadr/failovers/</guid><description>&lt;div class="alert alert-success" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;TL;DR&lt;/div&gt;&#10;&lt;p&gt;To avoid spurious failovers in an Always On environment, adjust these settings:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Lease Timeout&lt;/strong&gt;: raise it if your server goes through CPU load spikes.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;HealthCheck Timeout&lt;/strong&gt;: raise it if your server is slow to answer diagnostic requests.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;When you run AlwaysOn Availability Groups, it is not unusual to get spurious failovers while your system is working perfectly well.&lt;/p&gt;&#10;&lt;p&gt;It tends to happen at night, and more rarely during the day. The most common cause is a temporary unavailability of the system, which makes the cluster health checks time out. A typical example is a VM freeze while backup software takes a snapshot.&lt;/p&gt;</description></item></channel></rss>