Microsoft SQL Server Failover Cluster Instance and Basic Availability Group features comparison
Posted by Dima Yaprincev on November 9, 2017
5/5 (2)

Introduction

Microsoft SQL Server 2016 has a pretty decent feature set to achieve cost-effective high availability for your environment and build a reliable disaster recovery solution. Basic Availability Groups (BAGs) and Failover Cluster Instances (FCI) are included in SQL Server 2016 Standard Edition and serve to implement high redundancy level for business-critical databases. In this article, I would like to discuss some differences between these solutions and open the curtain on how it can be done with Software-Defined Storage like Storage Spaces Direct (S2D) and StarWind Virtual SAN (StarWind VSAN).

Failover Cluster Instance versus Basic Availability Group image

(more…)

Please rate this

Deploying SQL Server 2016 Basic Availability Groups Without Active Directory. Part 1: Building the Platform
Posted by Edwin M Sarmiento on October 31, 2017
5/5 (3)

Introduction

When Availability Groups were introduced in SQL Server 2012, they were only available in Enterprise Edition. This made it challenging to move from Database Mirroring to Availability Groups, especially if you’re running Standard Edition.  To upgrade and migrate from Database Mirroring in Standard Edition, you either choose to upgrade to a more expensive Enterprise Edition license and implement Availability Groups or stick with Database Mirroring and hope that everything works despite being deprecated.

SQL Server 2016 introduced Basic Availability Groups in Standard Edition, allowing customers to run some form of limited Availability Groups. Customers now have a viable replacement for Database Mirroring in Standard Edition. However, unlike Database Mirroring, Availability Groups require a Windows Server Failover Cluster (WSFC). SQL Server database administrators now need to be highly skilled in designing, implementing and managing a WSFC outside of SQL Server. Because the availability of the SQL Server databases relies heavily on the WSFC.

SQL Server 2016 logo

(more…)

Please rate this

Upgrading System Center Orchestrator 2012 R2 to 2016
Posted by Nicolas Prigent on July 11, 2017
5/5 (3)

Microsoft System Center Orchestrator logo

Orchestrator is a workflow management solution for the data center. Orchestrator lets you automate the creation, monitoring, and deployment of resources in your environment. Orchestrator is also known as “SCORCH” or “SCO”. Orchestrator uses a drag and drop graphical interface to allow admins to define runbooks. A runbook is a compilation of routine procedures and operations that Orchestrator will run depending on your scheduling. Finally, Orchestrator is capable of managing multiple operating systems.

After reading this guide, you should have a basic understanding of how to upgrade/install Orchestrator.

(more…)

Please rate this

Installing System Center Configuration Manager 1610 (Current Branch) on Windows Server 2016 with SQL Server 2016. PART 2
Posted by Nicolas Prigent on March 16, 2017
5/5 (6)

Microsofr System Center Configuration Manager

Thanks to the previous part, we have SQL Server 2016 installed and configured. Before running the SCCM installation process, let’s remember the architecture we are implementing.

(more…)

Please rate this