Yitzhak

My feedback

  1. 19 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 8

    <=-=Mar 4 2017 9:33AM=-=>

    We understand the problem. XML is designed differently and the goal was to provide rich query language with XPath support, which might require a lot of memory and processing logic. OPENJSON is designed to be more lightweight and just scan JSON text and return values where it finds them. There are pros and cons for both approaches (similar to pros and cons for DOM and SAX parsers).

    The key differentiators between JSON and XML is the fact that JSON is better for scan based processing of JSON columns where you just pick few values from JSON text, and XML is better for rich querying and indexing.

    I will keep this item open and let people vote for this; however, we cannot guarantee that this kind of re-design of XML will be done in near future.

    If you need to use shredded nodes in some…

    Yitzhak supported this idea  · 
  2. 303 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    60 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Yitzhak commented  · 

    Here is one of the prominent examples what we are facing from the www.stackoverflow.com:

    Convert nested XML via XQuery to flat xml
    https://stackoverflow.com/questions/58080659/convert-nested-xml-via-xquery-to-flat-xml

    An error occurred while saving the comment
    Yitzhak commented  · 

    Just relational is not enough today.
    Many applications today need both relational and not relational data model/functionality in the same application.

    An error occurred while saving the comment
    Yitzhak commented  · 

    The situation is even worse than I initially thought.
    SQL Server is stuck at the 2004 (15 years old) preliminary draft version of the XQuery 1.0 standard.

    Here is an excerpt from the XQuery Language Reference (SQL Server).

    "...Transact-SQL supports a subset of the XQuery language that is used for querying the
    xml data type. This XQuery implementation is aligned with the July 2004 Working Draft
    of XQuery. The language is under development by the World Wide Web Consortium
    (W3C), with the participation of all major database vendors and also Microsoft. Because
    the W3C specifications may undergo future revisions before becoming a W3C
    recommendation, this implementation may be different from the final recommendation..."

    Yitzhak supported this idea  · 
    Yitzhak shared this idea  · 
  3. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Logic Apps » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Yitzhak supported this idea  · 
  4. 1,012 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  398 comments  ·  SQL Server  ·  Flag idea as inappropriate…  ·  Admin →
    Yitzhak supported this idea  · 

Feedback and Knowledge Base