IT professional writing about cybersecurity, cloud & DevOps, automation, networking, and systems administration. Real-world guides for real-world problems.
The AG is built (Part 5). Now we verify it actually works: replication is happening, the secondary is receiving log records, reads work on the secondary (Enterprise readable secondary feature),…
This is the part where everything we built in Parts 1–4 finally becomes an Availability Group. Two SQL nodes, a Windows Failover Cluster, AlwaysOn enabled, demodb in FULL recovery with…
SQL Server is installed on both nodes (Part 2) and the WSFC is up (Part 3). Two more prerequisites before we can build the AG itself: Enable the Always On…
SQL Server Always On Availability Groups require a Windows Server Failover Cluster (WSFC) underneath. The AG itself doesn’t move shared storage around — it replicates databases. But the cluster service…
With both VMs built and joined to the domain in Part 1, the next step is installing SQL Server 2022 + SQL Server Management Studio (SSMS) on both nodes. Identical…
SQL Server Always On Availability Groups (AG) are the modern HA + DR primitive for SQL workloads. Two or more SQL nodes hold synchronized copies of the same database. A…
The Users may view their BitLocker keys toggle in Entra Device Settings is one of those security knobs where you don’t actually know it works until you test it end-to-end…
Microsoft Entra B2B Collaboration — part of the Entra External Identities feature set — lets you invite people from outside your tenant (partners, vendors, contractors) to access specific apps and…
