JSON Has a Cost

  • Comments posted to this topic are about the item JSON Has a Cost

  • I can't see any of the comments that were posted according to the discussion pages near the bottom of the article,

     

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Well that's interesting. Not sure where they are. I don't see them as hidden or reported as SPAM.

  • 100% agree with relational vs JSON, which is pretty much a rehash of hierarchical databases of the 1970s. Relational won the battle then, but people forget or never knew. See Michael Stonebraker's (and Joseph Hellerstein)  2005 What Goes Around Comes Around . Updated in 2024 BTW, What Goes Around Comes Around... And Around... by Stonebraker and Pavlo. (my original post included a link to PDF, which maybe this system doesn't like)

  • Steve Jones - SSC Editor wrote:

    Comments posted to this topic are about the item JSON Has a Cost, which is is not currently available on the site.

    Even this first topic forum reference doesn't have the articles URL referred to by its title

    JSON Has a Cost

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data and code to get the best help

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Who am I ? Sometimes this is me but most of the time this is me

  • Yeah, I was going to edit it, but filed a bug first

     

  • There are more complete and robust JSON database solutions, like Azure CosmosDB or MongoDB. If what the application needs to do is query rows for a specific customer or product and then get additional fields for that specific entity from a JSON document, then it seems a better architecture would be to query a fully normalized SQL Server table, while making a parallel asynchronous lookup in the document database, and then join the two results in the middle tier or client side.

     

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply