Tags » Always On


Modern life is like
A church, the religion

The prayer book, needs due reverence.
Wi-fi now the word of God.
© 2018 | Frank Regan, All rights reserved. 8 more words


How you SHOULD perform a manual fail-over of a SQL AlwaysOn Availability Group

Since the arrival of BizTalk Server 2016, Microsoft added support for SQL AlwaysOn. It still is new to many BizTalk operators, administrators and developers. Often having been dealing with older versions of BizTalk. 331 more words

BizTalk Server


his story owns him
the past, his costume and script
he is always “on”


Windows 2016 Failover Cluster Services now has load balancing (enabled by default)

Having a production system with “new technology” is always keen to give you some issues you didn’t know about earlier on.

Lately, due to the arrival of BizTalk Server 2016 and related support for Windows Server 2016 and SQL Server 2016, we’ve seen some things we did calculate for. 170 more words

BizTalk Server

Help: SQL Server Always On Availability Group Listener not working in Azure SQL VMs (Using Internal Load Balancer - ILB). How to troubleshoot?

As many of you might know that currently I have been supporting SQL Server in Azure Virtual Machines. Most of the concepts remains same but one of the common issue which was reported by many customer is about Always On listener connectivity. 507 more words


Sobre la Alta Disponibilidad en SQL Server

SQL Server 2014 incluye varias opciones para la implementación de alta disponibilidad. Estos incluyen el trasvase de registros, lo que refleja la base de datos y grupos de disponibilidad AlwaysOn para proteger las bases de datos, así como las instancias de clúster de conmutación por error de AlwaysOn, una tecnología que se basa en Windows Server Failover Clustering (WSFC), para proteger las instancias de SQL Server. 784 more words

Administración SQL

Note-To-Self: ICYMI, #MIM2016 Support for SQL Always On Availability groups

Based on a recent customer support experience with MIM (migrating from MIM 2016 RTM to SP1 latest hotfix), I ran into a few issues…

They have been documented here: 187 more words