• Grant Fritchey - Friday, February 9, 2018 8:07 AM

    Jeff Moden - Friday, February 9, 2018 6:39 AM

    Yowch... that sucks.  So much for temporary usage during the night for large ETL jobs.  Don't need it or even want it for anything else.

    I guess the workaround for me will be to create a temporary "scratch" database, do the work, and then drop that "scratch" database.

    Yeah, it has burned more than a few people. Still, memory optimized tables handy for table variables too. Just saying.

    I basically forbid the use of Table Variables because of their non-persistent nature for troubleshooting and the single row estimates they normally kick up unless you do a recompile.  The only place we use them is where we have to, such as in iTVFs.  I'm a bit new to the in-memory thing... is there a way to tell iTVFs to use In_Memory?  Is it a simple as creating the iTVFs on the in-memory group?

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