Book Image

SQL Server 2017 Administrator's Guide

4 (1)
Book Image

SQL Server 2017 Administrator's Guide

4 (1)

Overview of this book

Take advantage of the real power of SQL Server 2017 with all its new features, in addition to covering core database administration tasks. This book will give you a competitive advantage by helping you quickly learn how to design, manage, and secure your database solution. You will learn how to set up your SQL Server and configure new (and existing) environments for optimal use. After covering the designing aspect, the book delves into performance-tuning aspects by teaching you how to effectively use indexes. The book will also teach you about certain choices that need to be made about backups and how to implement a rock-solid security policy and keep your environment healthy. Finally, you will learn about the techniques you should use when things go wrong, and other important topics, such as migration, upgrading, and consolidation, are covered in detail. Integration with Azure is also covered in depth. Whether you are an administrator or thinking about entering the field, this book will provide you with all the skills you need to successfully create, design, and deploy databases using SQL Server 2017.
Table of Contents (13 chapters)

Always On Availability Groups

Always On Availability Groups is a high availability and disaster recovery feature that was introduced in SQL Server 2012. This feature, similar to Always On Failover Cluster Instances, requires a Windows Server Failover Clustering (WSFC) to be configured on the nodes running on the SQL Server. Availability Groups work at a database level, where the Always On Failover Cluster Instances (FCI) are protecting the whole instance.

We won't focus on the WSFC anymore and just use the common platform to deploy the SQL Server Always On Availability Groups in the following scenarios through the chapter. The WSFC configuration for the Availability Groups is more simple when compared to the FCI infrastructure, since Availability Groups don't require any shared storage and the storage solution depends on the node type. To utilize the Availability Groups...