SQL Server vNext (post 2019) and NoSQL functionality

[ykhabins]

Hello,

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 UTF-8 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.

[#2]

Hi @ykhabins ,

The forums best fit for specific question or dicussion with the community. For feedback and request regarding the product future development, I recommend to use the "USER VOICE" system. You can get more information in the following page.

Or go the SQL Server User Voice directly using this link.

Once you open a feedback, you can publish the link here

[#3]

Hi @Ronen_Ariely 

Based on the Ronen Ariely suggestion, I posted the same request on the SQL Server feedback site here:

https://feedback.azure.com/forums/908035-sql-server/suggestions/38142115-sql-server-vnext-post-2019-...

Please go there and vote for it.