ISJSON

  • Igor Micev

    SSC-Dedicated

    Points: 33109

    Comments posted to this topic are about the item ISJSON

    Igor Micev,
    My blog: www.igormicev.com

  • This was removed by the editor as SPAM

  • Terje Hermanseter

    Hall of Fame

    Points: 3804

    Since we don't have a 2016 server that I could test this on, I tried to read the documentation for clues. Found this article, https://msdn.microsoft.com/en-us/library/dn246937.aspx, but sadly it didn't say anything about JSON. So I chose the wrong answer 😛

  • TimCarrett

    Default port

    Points: 1484

    As I haven't used In Memory tables yet I did a search on this I found the following:

    https://blogs.technet.microsoft.com/dataplatforminsider/2016/01/06/json-in-sql-server-2016-part-2-of-4/

    Which implies that ISJSON is available in SQL Server 2016 for In Memory tables? Could you confirm if it is or not?

  • paul.knibbs

    SSCoach

    Points: 15270

    Terje Hermanseter (6/6/2016)


    Since we don't have a 2016 server that I could test this on, I tried to read the documentation for clues. Found this article, https://msdn.microsoft.com/en-us/library/dn246937.aspx, but sadly it didn't say anything about JSON. So I chose the wrong answer 😛

    Yeah, I couldn't find any documentation for this and don't have a handy 2016 instance, so I also picked the wrong one--I thought the question might be asking about the general inability to alter the table schema of a memory-optimised table, for which constraints are an exception. Learned something, though, which is always good.

    I suppose the obvious question is, though: WHY is this limitation there?

  • david.dilworth

    Right there with Babe

    Points: 780

    I also chose the wrong answer after a bit of googling that included finding the exact page referred to in the answer.

    So my question is how would you find out about this from the MSDN documentation?

  • Igor Micev

    SSC-Dedicated

    Points: 33109

    TimCarrett (6/6/2016)


    As I haven't used In Memory tables yet I did a search on this I found the following:

    https://blogs.technet.microsoft.com/dataplatforminsider/2016/01/06/json-in-sql-server-2016-part-2-of-4/

    Which implies that ISJSON is available in SQL Server 2016 for In Memory tables? Could you confirm if it is or not?

    I was looking at that article too. The article says that JASON can be stored in In-Memory table that is absolutely true, but the constraint cannot be created when the table is In-Memory enabled.

    Igor Micev,
    My blog: www.igormicev.com

  • Igor Micev

    SSC-Dedicated

    Points: 33109

    Terje Hermanseter (6/6/2016)


    Since we don't have a 2016 server that I could test this on, I tried to read the documentation for clues. Found this article, https://msdn.microsoft.com/en-us/library/dn246937.aspx, but sadly it didn't say anything about JSON. So I chose the wrong answer 😛

    I too, was looking at that documentation but didn't find about the JASON() function.

    Igor Micev,
    My blog: www.igormicev.com

  • sestell1

    SSChampion

    Points: 10230

    Thanks Igor for the interesting question.

    This is definitely good to know, since it doesn't seem to be documented anywhere. :crazy:

  • Revenant

    SSC-Forever

    Points: 42467

    I guess I am just lucky that I work with JSON daily. 🙂

    Thanks, Igor!

  • SQL_Hunt

    SSC-Dedicated

    Points: 33267

    JSON is supported in SQL 2016, but could not find such restriction with a mix of JSON with In Memory OLTP. It is in the beginning stage to tick the right answer.

    Thanks.

  • HappyGeek

    SSCoach

    Points: 18666

    Did do research and found nothing, got it wrong too, looking at the stats makes it the same as a toss of a coin over time................. evens

    ...

  • Carlo Romagnano

    SSC-Insane

    Points: 21793

    TimCarrett (6/6/2016)


    As I haven't used In Memory tables yet I did a search on this I found the following:

    https://blogs.technet.microsoft.com/dataplatforminsider/2016/01/06/json-in-sql-server-2016-part-2-of-4/

    Which implies that ISJSON is available in SQL Server 2016 for In Memory tables? Could you confirm if it is or not?

    I also found this article. It seems that it's supported. But I can't try.

  • TomThomson

    SSC Guru

    Points: 104772

    sestell1 (6/6/2016)


    Thanks Igor for the interesting question.

    This is definitely good to know, since it doesn't seem to be documented anywhere. :crazy:

    In particular, it's not documented in the "good discussion for JSON" referenced in the explanation. And that discussion contains the statement Hekaton and Columnstore don't support LOBs, which suggests that the table declaration with an NVARCHAR(MAX) column and asking for Memory_Optimised should have failed and the statement introducing the second constraint never executed, so since that statement is executed and fails for an unmentioned reason should I conclude that this "good discussion" is rather out of date? :unsure:

    Tom

  • Ed Wagner

    SSC Guru

    Points: 286958

    There are a whole bunch of restrictions for memory-optimized tables and most of them that I remember are about performance. It prevents us from creating tables that are going to be slow by design. Granted, all my knowledge is theoretical because I've seen PASS presentations on it, but we're nowhere near getting SQL 2016 in-house. Even if we did, it takes EE anyway and I'm not that fortunate.

Viewing 15 posts - 1 through 15 (of 18 total)

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