Book Image

Introducing Microsoft SQL Server 2019

By : Kellyn Gorman, Allan Hirt, Dave Noderer, Mitchell Pearson, James Rowland-Jones, Dustin Ryan, Arun Sirpal, Buck Woody
Book Image

Introducing Microsoft SQL Server 2019

By: Kellyn Gorman, Allan Hirt, Dave Noderer, Mitchell Pearson, James Rowland-Jones, Dustin Ryan, Arun Sirpal, Buck Woody

Overview of this book

Microsoft SQL Server comes equipped with industry-leading features and the best online transaction processing capabilities. If you are looking to work with data processing and management, getting up to speed with Microsoft Server 2019 is key. Introducing SQL Server 2019 takes you through the latest features in SQL Server 2019 and their importance. You will learn to unlock faster querying speeds and understand how to leverage the new and improved security features to build robust data management solutions. Further chapters will assist you with integrating, managing, and analyzing all data, including relational, NoSQL, and unstructured big data using SQL Server 2019. Dedicated sections in the book will also demonstrate how you can use SQL Server 2019 to leverage data processing platforms, such as Apache Hadoop and Spark, and containerization technologies like Docker and Kubernetes to control your data and efficiently monitor it. By the end of this book, you'll be well versed with all the features of Microsoft SQL Server 2019 and understand how to use them confidently to build robust data management solutions.
Table of Contents (15 chapters)

Diagnostics and advanced options

The Advanced tab lets you update to Ephemeral OS disks, which only save to the local VM storage and work great for stateless workloads, as they don't save to Azure cloud storage.  Once you've made these decisions, you then progress to virtual networking. A VNet is then used to connect to the network interface (NIC) and the Azure cloud.

If a VNet already exists in the resource group, location, and subscription tenant, then a VM can use it. This will mean you won't have to deploy a new one just for the VM. Workload traffic should be discussed as part of the decision to use an existing VNet or deploy a new one as part of the VM.

The VNet will deploy public and private IP addresses to be used by the VM for access. These addresses must be associated with the VM by assigning them to the NIC. Inside each VNet, there is a subnet (or subnets) that follows rules for allocating traffic in and out of the VM. If a rule hasn't...