Book Image

Mastering SQL Server 2017

By : Miloš Radivojević, Dejan Sarka, William Durkin, Christian Cote, Matija Lah
Book Image

Mastering SQL Server 2017

By: Miloš Radivojević, Dejan Sarka, William Durkin, Christian Cote, Matija Lah

Overview of this book

Microsoft SQL Server 2017 uses the power of R and Python for machine learning and containerization-based deployment on Windows and Linux. By learning how to use the features of SQL Server 2017 effectively, you can build scalable apps and easily perform data integration and transformation. You’ll start by brushing up on the features of SQL Server 2017. This Learning Path will then demonstrate how you can use Query Store, columnstore indexes, and In-Memory OLTP in your apps. You'll also learn to integrate Python code in SQL Server and graph database implementations for development and testing. Next, you'll get up to speed with designing and building SQL Server Integration Services (SSIS) data warehouse packages using SQL server data tools. Toward the concluding chapters, you’ll discover how to develop SSIS packages designed to maintain a data warehouse using the data flow and other control flow tasks. By the end of this Learning Path, you'll be equipped with the skills you need to design efficient, high-performance database applications with confidence. This Learning Path includes content from the following Packt books: SQL Server 2017 Developer's Guide by Miloš Radivojevi?, Dejan Sarka, et. al SQL Server 2017 Integration Services Cookbook by Christian Cote, Dejan Sarka, et. al
Table of Contents (20 chapters)
Title Page
Free Chapter
1
Introduction to SQL Server 2017

Why JSON?

The Microsoft Connect site is the place where you can leave your feedback, suggestions, and wishes for Microsoft products. The most popular feature request for SQL Server is the one for JSON support. It was created in June 2011 and at the time of writing (October 2017) it has 1,138 votes. The request is still open, as you can see in the following screenshotand you will see later in this chapter, why it still makes sense to have it in the active state:

Highly ranked requests for SQL Server on the Microsoft Connect site (October 2017)

What arguments are used by community members to justify the request? They are as follows:

  • JSON is already standard, and it should be supported, similar to XML.
  • Other vendors support it (Oracle, PostgreSQL, and others)
  • Due to the lack of JSON support, my customers want to move from SQL Server to other database systems supporting JSON...