Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
SQL Server 2017 Developer???s Guide

You're reading from   SQL Server 2017 Developer???s Guide A professional guide to designing and developing enterprise database applications

Arrow left icon
Product type Paperback
Published in Mar 2018
Publisher Packt
ISBN-13 9781788476195
Length 816 pages
Edition 1st Edition
Languages
Arrow right icon
Authors (3):
Arrow left icon
Dejan Sarka Dejan Sarka
Author Profile Icon Dejan Sarka
Dejan Sarka
Miloš Radivojević Miloš Radivojević
Author Profile Icon Miloš Radivojević
Miloš Radivojević
William Durkin William Durkin
Author Profile Icon William Durkin
William Durkin
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Introduction to SQL Server 2017 FREE CHAPTER 2. Review of SQL Server Features for Developers 3. SQL Server Tools 4. Transact-SQL and Database Engine Enhancements 5. JSON Support in SQL Server 6. Stretch Database 7. Temporal Tables 8. Tightening Security 9. Query Store 10. Columnstore Indexes 11. Introducing SQL Server In-Memory OLTP 12. In-Memory OLTP Improvements in SQL Server 2017 13. Supporting R in SQL Server 14. Data Exploration and Predictive Modeling with R 15. Introducing Python 16. Graph Database 17. Containers and SQL on Linux 18. Other Books You May Enjoy

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 screenshot, and 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.

As always with vox populi (the opinions or beliefs of the majority), some of the arguments and given examples represent development...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime