In memory tables

  • I am looking use in memory tables and I read that it is supported on AOAG and transactional replication environment. Is there any addition configuration need to be done for the in memory tables while doing the failover and using transactional replication?

  • I can't answer your question but my question would be, "Why"?  What problem are you trying to solve with "In Memory" tables?

    The reason I ask is because I've made 20 million row, fairly complex aggregations/Cross Tabs on a 100 million row table, 52.3 GB table that used to take 8 seconds and 10.5GB of I/O drop down to 11 ms (milli-seconds) duration and only use 0.781 MB  (100 pages) of I/O without having to muck about with In-Memory or column store stuff.

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

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

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