• 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.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning