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)

The storage account

Typically, you would set up your storage account as shown in Figure 4.1:

Figure 14.1: Setting up the storage account
Figure 4.1: Setting up the storage account

You should create containers to organize the contents of your storage account. There are two types of blob storage that you could use, these being page and block blobs (technically, there is another blob type, called append blob, which will not be covered in this chapter). The type of blob you use is dictated by the security route that you take. If you decide to use a storage key within the SQL Server credential, then page blobs will be used; if you configure an SAS for the credential, then block blobs will be used. The best practice is to use block blobs for three main reasons. Firstly, using an SAS is a more secure way than using a storage key to authorize access to blob storage. It provides a more granular level of access without the need to expose the main storage account keys (primary or secondary). With block blobs...