June 5, 2016 at 11:04 pm
This was removed by the editor as SPAM
June 6, 2016 at 1:40 am
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 😛
June 6, 2016 at 1:41 am
As I haven't used In Memory tables yet I did a search on this I found the following:
Which implies that ISJSON is available in SQL Server 2016 for In Memory tables? Could you confirm if it is or not?
June 6, 2016 at 2:00 am
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?
June 6, 2016 at 2:35 am
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?
June 6, 2016 at 3:32 am
TimCarrett (6/6/2016)
As I haven't used In Memory tables yet I did a search on this I found the following: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
June 6, 2016 at 3:45 am
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
June 6, 2016 at 7:05 am
Thanks Igor for the interesting question.
This is definitely good to know, since it doesn't seem to be documented anywhere. :crazy:
June 6, 2016 at 8:48 am
I guess I am just lucky that I work with JSON daily. 🙂
Thanks, Igor!
June 6, 2016 at 11:18 am
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.
June 6, 2016 at 11:27 am
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
...
June 7, 2016 at 2:26 am
TimCarrett (6/6/2016)
As I haven't used In Memory tables yet I did a search on this I found the following: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.
June 7, 2016 at 7:28 am
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
June 7, 2016 at 9:16 am
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 17 total)
You must be logged in to reply to this topic. Login to reply