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.
I think XML would be a great addition!
Excellent Suggestion !
Simon Gregory commented
How about BSON support
Ariel Rico commented
Please do this.
Very nice idea.
+ 1 for continued support for XML standards.
Evan Lenz commented
I would also like to see Microsoft create a modern XSLT implementation. As a consultant, I unfortunately have to recommend alternatives to Microsoft's outdated technology.
Yes. I'm expecting to see a resurgence of XML interest.
I loved that idea!!
Ram Jaddu commented
john john bogaert commented
I use FOR XML,JSON to generate PDF with Apache FOP, XPath 3.1 would be a nice update
I also would like the reg exp full support in native functions LIKE PATINDEX
Mohammed sajid commented
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.
very good idea.
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 !