• Grant Fritchey (4/29/2014)


    The thing is, I think the technology is amazing, but, it's really all about the ability to collect data and feed data out at high speed in an OLTP environment. Way too many people are going to think that it solves all sorts of problems that it doesn't. It's not a panacea. In fact, it's extremely focused in the problems it can solve. But, I think it solves those problems well. But, again, you have to have big enough machines to really make it work. We're still getting all sorts of questions from people running on an 8gb server. They're not going to implement in-memory anything any time soon. It's a niche solution, albeit a pretty cool one. But no, no immediate plans because we're no where near the target audience and don't have the kind of hardware necessary to make the whole thing work.

    I absolutely agree. It is both a niche and nice solution for high speed OLTP and a lot of people are thinking of it more as a general purpose RAM disk, which it isn't. It's very targeted and does well for what it was designed for. I do wish it had IDENTITY column capabilites, though.

    --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)