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)

Log shipping

Log shipping is a disaster recovery technology, as there is no automatic failover available with this solution. With database configured for log shipping, there are several automated jobs that periodically back up the transaction log and restore the log to a different server. This server can be used for many scenarios like:

  • Disaster recovery
  • Reporting offload

Disaster recovery configuration is mainly used for a warm standby server, which has data nearly synchronized with the master server and can be brought up quite quickly providing we have all the backups available up to the point of the disaster. Log shipping has quite a simple architecture, where you have only two main server roles--primary and secondary. With log shipping, you can configure more secondary servers that will host the database for DR scenarios for warm standby or reporting, similar to replication...