Store JSON data in SQL Server 2016

Question

Post reply

Store JSON data in SQL Server 2016

Evgeny Garaev

SSCertifiable

Points: 7428
More actions
January 28, 2018 at 12:02 am

#335629

Comments posted to this topic are about the item Store JSON data in SQL Server 2016

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

HappyGeek SSCoach Points: 18729 More actions · Answer 1

HappyGeek

SSCoach

Points: 18729

January 28, 2018 at 12:03 am

#1977632

Good question thanks Evgeny.

...

Stewart "Arturius" Campbell SSC Guru Points: 72624 More actions · Answer 2

Nice question to start the week on, thanks Evgeny

____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”

Thomas Franz Hall of Fame Points: 3893 More actions · Answer 3

I'm confused - the MS page you linked in your answer says in its head:
THIS TOPIC APPLIES TO: yes SQL Server (starting with 2016)

So why should I not use the JSON datatype?

God is real, unless declared integer.

HappyGeek SSCoach Points: 18729 More actions · Answer 4

t.franz - Monday, January 29, 2018 2:08 AM
I'm confused - the MS page you linked in your answer says in its head:
THIS TOPIC APPLIES TO: SQL Server (starting with 2016)
So why should I not use the JSON datatype?

There is no JSON data type in SQL2016, I understand the idea was bounced for reasons of customer convenience although I cannot find the link at the moment...or perhaps I can as on here

...

Kaye Cahs SSCarpal Tunnel Points: 4135 More actions · Answer 5

t.franz - Monday, January 29, 2018 2:08 AM
I'm confused - the MS page you linked in your answer says in its head:
THIS TOPIC APPLIES TO: SQL Server (starting with 2016)
So why should I not use the JSON datatype?

The page describes how to process JSON data using the built-in functions that are available in SQL Server 2016. However, there is no JSON datatype as such. As the examples show, the JSON text itself is stored in NVARCHAR(MAX) columns in the tables.
Hope that helps.

Aleksl-294755 Hall of Fame Points: 3514 More actions · Answer 6

Aleksl-294755

Hall of Fame

Points: 3514

January 30, 2018 at 7:49 am

#1977859

Great question. I didn't know that. Thanks Evgeny

Eric M Russell SSC Guru Points: 125561 More actions · Answer 7

As a side note, if what you really need to do is store a collection of JSON documents and work with the data natively as a JSON objects, arrays, properties, etc., then consider DocumentDB (Microsoft Cosmos DB).

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Wade Anderson Newbie Points: 1 More actions · Answer 8

Eric M Russell - Tuesday, January 30, 2018 8:30 AM
As a side note, if what you really need to do is store a collection of JSON documents and work with the data natively as a JSON objects, arrays, properties, etc., then consider DocumentDB (Microsoft Cosmos DB).

Just be aware that the charges for DocumentDB (Azure) are probably more than they are for SQL. I tried some of the document stuff on Azure and it was very expensive for whatever reason.