News for hackers. Stuff that matters.
Re:JSON Support in SQL Server 2016 by manigandham on Tuesday May 19, 2015 @01:53PM (#9571871)
What's the best use case for this? I've seen lots of requests but I'm struggling to find a really good scenario beyond just avoiding the work of normalizing into regular DB tables and all the schema management that comes with it (which isn't necessarily a bad thing).

Any top level fields can just be made columns and we already have 1:M and M:M mappings done well in relational tables, is it purely just being able to serialize into 1 field and then query on that? Why not just use a document database then?

There are no comments on this comment yet.