SQL Server 2016 and JSON Support

Play SQL Server 2016 and JSON Support
Sign in to queue

Description

In this episode of Data Exposed Scott welcomes to the show Jovan Popovic to the show, Program Managers in the SQL Server group. Today Jovan is in the studio all the way from the Microsoft offices in Serbia to talk about the awesome topic of JSON in SQL Server 2016 and Azure SQL DB. The show begins with asking and answering the question of why JSON support in SQL Server 2016, and Jovan does a great job providing insight into how and where JSON is being used today and why it makes sense to include support for JSON in SQL Server.
 
At the 1:50 mark, Jovan shows us how JSON is implemented in SQL Server, the built in functions and operators, such as how to get or modify a JSON value or even checking if the the JSON is valid or not, and how easy it is to format data to and from JSON and to read and write data to and from SQL Server. Jovan explains that JSON is very lightweight and simple, and much better to work with than XML.
 
At the 5:50 mark Jovan dives a little deeper into the JSON built-in functions by showing us some examples and explaining how they work and what we can expect. He then spends a few minutes how each of these functions can be used in typical T-SQL queries, for example adding them in SELECT or WHERE clauses. Very awesome.
 
Finally, at the 9:30 mark, Jovan spends the remaining 20 minutes in full demo mode, showing us real-time how to use these functions including OPENJSON, JSON_MODIFY, ISJSON, and more! 20 minutes of demos on how flexible and awesome support for JSON in SQL Server 2016.
 
Great introduction into SQL Server JSON support. We look forward to having Jovan back for more videos on this topic!

https://www.microsoft.com/en-us/evalcenter/evaluate-sql-server-2016
 
https://www.microsoft.com/en-us/server-cloud/products/sql-server/

Embed

Download

Right click to download this episode

The Discussion

  • User profile image
    jkresic1

    I'm only 22 minutes into the video, and I am amused that I heard Jason Bourne when they were discussing @json, '$.Born',    !

  • User profile image
    mrsharps

    I LOVE how he is doing the examples! I like that most typical use cases with increasing difficulty get covered one by one.  Great intro video.  Well done!

  • User profile image
    Alex

    What shortcut to converts the JSON single line result into formatted JSON?

  • User profile image
    Celso

    Can somebody please help me out in What shortcut to converts the JSON single line result into formatted JSON?

  • User profile image
    keradininis

    Great tutorial, at a perfect pace.

    Thank you

  • User profile image
    keradininis

    @Celso:Use Sql Operations Studio. It works there.

  • User profile image
    aaa

    a

  • User profile image
    heena bhalodia

    Code :-
    --------------------------------------

    DECLARE @Json NVARCHAR(MAX) = '
    [
    {
    "RigthNumber":"RC01","RowVersion":[0,0,0,0,0,87,205,88]
    },
    {
    "RigthNumber":"RC02","RowVersion":[0,0,0,0,0,87,205,89]
    }
    ]
    '

    SELECT RigthNumber
    ,RowVersion
    FROM
    OPENJSON (@Json)
    WITH (
    RigthNumber varchar(50) '$.RigthNumber'
    ,RowVersion timestamp'$.RowVersion'
    )

    Current OutPut (Wrong Data in RowVersion)
    -------------------------------------------
    RigthNumber RowVersion
    RC01 0x
    RC02 0x


    Expected OutPut
    -----------------
    RigthNumber RowVersion
    RC01 0x000000000057CD8C
    RC02 0x000000000057CD8D

    Query : i dont get proper data for timestamp data type,can you help me?
    datatype of RowVersion is timestamp

  • User profile image
    apoovendran

    Very good explanation. Thanks.

  • User profile image
    Yotafreak
    json, '$.Born' will be the new Jason Bourne working title in 2019 :P
  • User profile image
    Suhaskoorse
    Could you please paste the SQL code, So I could try out.
    Appreciate your help this is great
  • User profile image
    ewealks
    @Celso:
    In Visual Studio, hit Enter (or Return Key) at the end of the JSON text

Add Your 2 Cents