AlwaysOn

Help yourself out with the ‘log_reuse_wait_desc’ column

A few days ago a customer called me to ask if I could help him with a problem with the log file. He tried to shrink it, but the system wasn’t doing anything and he didn’t know why. With the column(…)

SQL Server: Basic AG – One listener, multiple databases

Introduction When it is not possible to have SQL Server Enterprise and there is a need to set up an AlwaysOn cluster, it is possible to use SQL Server Standard and implement basic availability groups. However, the Standard edition of(…)

Move SQL Server database files to different folders with PowerShell

In my previous post, I explained how to move SQL Server databases files programmatically by leveraging the high availability of an Availability Group (AG).But when you can afford to have a database unavailable for a short time, and if(…)

Move secondary database files in SQL Server AG with PowerShell

For some circumstances, you may want to move data and log files for a database to a different location.Usually, this operation has to be made offline. But with an Availability Group (AG) environment, it is possible to choose an approach(…)

Automate CNOs and VCOs for SQL Server AAG

During the installation of a new SQL Server environment in a Project, we wanted to automate the whole process deployment and configuration when installing a new SQL Server Always On Availability Group (AAG). This installation requires to prestage cluster(…)

SQL Server AlwaysOn node “Add all eligible storage to the cluster”

I made a mistake recently when adding a new node to an existing Windows Failover Cluster supporting AlwaysOn SQL Server instances. When adding a new node using the GUI there’s this option checked by default named “Add all eligible storage(…)

SQL Server – Collecting last backup information in an AlwaysOn environment

Introduction Sometimes you face interesting challenges with unusual environment. One of my customer needed a automated and flexible backup solution. Said like that nothing very complex you will say. But if I mention that some databases were 60TB big with(…)

SQL Server 2017 AlwaysOn AGs and new read-scale architectures

As you probably know Microsoft announced an official name for SQL Server vNext during the last Microsoft Data Amp event on April 19 2017. It becomes officially SQL Serve 2017. In my first(…)

SQL Server AlwaysOn – Distributed availability groups, read-only with round-robin capabilities

This blog post comes from a very interesting discussion with one of my friends about the read-only capabilities of secondary replicas in the context of distributed availability groups. Initially, distributed availability groups are designed to address(…)

SQL Server 2016: Distributed availability groups and Cross Cluster migration

How to migrate an environment that includes availability groups from one Windows Failover Cluster to another one? This scenario is definitely uncommon and requires a good preparation. How to achieve this task depends mainly of your context. Indeed, we may(…)