Can't delete memory optimized tables
Hey everyone! We have a problem that is unsolvable for us. I hope that someone has already had this case or has enough expertise to find a solution for it. Introduction: We did a reallocation of de databasefiles (.mdf) and the logfiles (.ldf). We wanted to split all databasefiles to a datadrive and all logfiles to a logdrive. Apparently some days later one specific database reached the Suspect-mode: We were able to get the database back online through creating a new database with the existing logfile and databasefile. Apparently some of the tables are memory-optimized and no longer work. We have to delete these specific memory optimized tables, but we were not able to do that: We tried everything, even restoring the missing "memory optimized db" files: Dropping the mem_opt_filegroup first also fails (seems to happen because the mem_opt_filegroup is a restore from 3 months ago): As a side info, I am on a restore in an isolated environment. Thank you in advance for any support.
Unable to issue alter table for a memory optimized tables
First published on MSDN on May 10, 2017 Recently I assisted on a customer issue where customer wasn’t able to alter a memory optimized table with the following error Msg 41317, Level 16, State 3, Procedure ddl, Line 4 [Batch Start Line 35]A user transaction that accesses memory optimized tables or natively compiled modules cannot access more than one user database or databases model and msdb, and it cannot write to master.Solve your tempdb problems with memory optimized tables
First published on MSDN on Mar 25, 2016 if you are on SQL Server 2014 and above and have tempdb problems, SQL Server In-Memory OLTP Program Manager Jos de Bruijn just posted a great blog titled “Improving temp table and table variable performance using memory optimization”.
