Home Forums SQL Server 2014 Administration - SQL Server 2014 Ideal table for Memory Optimization ? RE: Ideal table for Memory Optimization ?

  • April 1, 2014 at 6:32 pm

    #1702296

    GilaMonster (4/1/2014)

    In-memory OLTP (hekaton) is for heavy concurrent load (tens of thousands of concurrent connections with thousands of inserts/sec). The advantage is the lock-less, latch-less optimistic concurrency. It's not a silver bullet for performance in all circumstances.

    I'm curious. Why wouldn't it run as fast as a normal table that's been cached?

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