SQL Server vNext (post 2019) and NoSQL functionality
This is an invitation for discussion to the SQL Server engine team and the community.
IMHO, SQL Server vNext (post 2019) should beef up its NoSQL functionality.
Specifically, its XML APIs.
This area is dormant since 2005/2008 release.
SQL Server currently supports the following:
- a subset of XQuery 1.0, circa 2007
- a subset of XPath 2.0, circa 2007
- XSD 1.0 circa 2001
The current w3c standards:
- XQuery 3.1
- XPath 3.1
- XSD 1.1 circa 2012
Everything is in place, even current support for the UTF-8 encoding in 2019.
Famous Obamacare is implemented by using MarkLogic as its DB, since the initial relational Oracle DB implementation failed the mission.
Just imagine if it had been MS SQL Server.
SQL Server is ready to move beyond pure relational DB.
Peter Villadsen commented
I have several scenarios where I am using BaseX, a dedicated XML database, in an environment where SQL Server is running. I attempted to use the XML support, but the performance and functionality were too far behind the curve, so I had to give up on it. This seems a shame. We really need a database that support multiple paradigms well: Cosmos does JSon and graphs well, but not relational or XML. The only thing SQL server does well is relational - The graph support in SQL Server that would be massively useful in our ERP system does not seem to have been maintained for a long time now, and is nowhere near a state where it can be used for real business scenarios.
Good idea indeed
Liam Quin commented
There were fears at the time that adding more of XQuery would confuse users, because of "for" and "if" and other things present inboth SQL and XQuery. I was never convinced by this.
Excellent Suggestion !
Suraj Kumar commented
As per the @ZoharPeled suggestion I also want better json support as it is widely used now a days.
Damir Matesic commented
Zohar Peled commented
I would also like to see better Json support than what we had since 2016 version - though it is a very impressive start, nested json objects and json arrays support still could use some upgrading
Bevan, John commented
I know that the .Net community (which has a lot of overlap with the MS SQL community given all those working on the MS stack) are also keen to see progress in this area.
I'm not sure how SQL is architected, but perhaps there's sufficient overlap in the code base for the teams to join efforts / get more value back from this investment?
A call was taking to not implement XPath 2.0 in .Net back in 2004: https://blogs.msdn.microsoft.com/dareobasanjo/2004/05/13/why-you-wont-see-xslt-2-0-or-xpath-2-0-in-the-next-version-of-the-net-framework/
Since then support for XPath 2 and 3 (and related functionality under the XML namespace) has become one of the most requested features, e.g. on the .Net Core GitHub Issues page, first raised in 2015: https://github.com/dotnet/corefx/issues/2295
Great idea and Necessary Suggestion
Lumisol Pedrozo commented
I agree and support this improvement.
Alex Grinberg commented
I like this idea and going to support it
This would be a great idea for the database world where there are differents requirements that need to be satisfied.
Good idea !
John Miner commented
The current version of the standards should be supported in the engine.
Ilia Odintsov commented
I hope this will help to switch SQL Server to latest XML standards. And XSLT support would be great.