Book Image

SQL Server on Azure Virtual Machines

By : Joey D'Antoni, Louis Davidson, Allan Hirt, John Martin, Anthony Nocentino, Tim Radney, Randolph West
Book Image

SQL Server on Azure Virtual Machines

By: Joey D'Antoni, Louis Davidson, Allan Hirt, John Martin, Anthony Nocentino, Tim Radney, Randolph West

Overview of this book

Deploying SQL Server on Azure virtual machines allows you to work on full versions of SQL Server in the cloud without having to maintain on-premises hardware. The book begins by introducing you to the SQL portfolio in Azure and takes you through SQL Server IaaS scenarios, before explaining the factors that you need to consider while choosing an OS for SQL Server in Azure VMs. As you progress through the book, you'll explore different VM options and deployment choices for IaaS and understand platform availability, migration tools, and best practices in Azure. In later chapters, you'll learn how to configure storage to achieve optimized performance. Finally, you'll get to grips with the concept of Azure Hybrid Benefit and find out how you can use it to maximize the value of your existing on-premises SQL Server. By the end of this book, you'll be proficient in administering SQL Server on Microsoft Azure and leveraging the tools required for its deployment.
Table of Contents (10 chapters)
8
Index

Hybrid scenarios

Taking what you've learned from this book up to this point, including the earlier parts of this chapter, you can start to build a picture in your mind of how SQL Server on an Azure VM can help you with creating a hybrid solution at any scale.

Whether for read-scalability, migration, or disaster recovery, you can run your on-premises SQL Server instance on Windows Server and have the same workload in SQL Server on an Azure VM at the same time.

Keep in mind that with Software Assurance, the free passive SQL Server replica can be used to synchronize with your primary replica (using asynchronous commit and manual failover) and run these maintenance operations:

  • Database consistency checks
  • Full and transaction log backups
  • Monitoring resource usage data

Additionally, you can run disaster recovery testing every 90 days with primary and disaster recovery replicas running simultaneously for brief periods.

Should you desire additional operations...