From BOL, my understanding is that DBAs do not need to administer DLLs created for memory optimized tables, or natively compiled stored procedures, as they are recompiled automatically, when the SQL Server service starts and are removed when no longer needed. But I am witnessing, that even after a memory optimized table has been dropped, and the service restarted, the DLLs still exist in the file system AND are still loaded into SQL memory and attached to the process. This can be witnessed by the fact that they are still visible in sys_dm_os_loaded_modules, and are locked in the file system if you try to delete them, whilst the SQL Service is running.

Is this a bug? Or are they cleaned up at a later date? If at a later date, what triggers the clean-up, if it isn't an instance restart?

1 Answer 1


Is this a bug?

No it is not a bug. Its by design. They are kept for troubleshooting and supportability purposes.

From the SQL_Server_2014_In-Memory_OLTP White_Paper

Database administrators do not need to maintain the files that are generated by native compilation. SQL Server automatically removes generated files that are no longer needed, for example on table and stored procedure deletion, and on drop database, but also on server or database restart.

I tried to repro your scenario on SQL Server 2014 + RTM + (Build12.0.2000.8) - Dev Edition server by creating a test memory optimized table and checking the dll loaded using

     SELECT name, description FROM sys.dm_os_loaded_modules
WHERE description = 'XTP Native DLL'

After I dropped my table, the dll still appears in the output of above select statement and the files are still in the folder and after restart they are still there too.

From Books Online -

No user interaction is needed to manage these files (.c, .obj, .xml, .pdb., .dll). SQL Server will create and remove the files as necessary.

SO I guess, we just have to follow what Microsoft says - SQL server will manage them for us :-)


I managed to clean up the old files by

  • Issuing a manual CHECKPOINT on the database.
  • Taking database offline and then bringing it online.

Ideally, you should not be restarting the server instance, just manual checkpoint and offline/online of the database will clear the files.

e.g. Repro :

USE master
create database db1
ALTER DATABASE db1 ADD FILEGROUP db1_mod CONTAINS memory_optimized_data
-- adapt filename as needed
ALTER DATABASE db1 ADD FILE (name='db1_mod', filename='D:\SQLServer2014\MSSQL12.SQL2014\MSSQL\DATA\db1_mod') -- change here as per your need !!
USE db1
(c1 int not null primary key nonclustered,
c2 int)

--- now check if the dll is loaded or not

SELECT name, description FROM sys.dm_os_loaded_modules WHERE description = 'XTP Native DLL'

enter image description here

--- now drop table and do a manual checkpoint

use db1;
drop table dbo.t1;

Still the module is loaded in memory (even server restart will load the module sometimes)

enter image description here

The (.c, .obj, .xml, .pdb., .dll) are still present in the folder :

enter image description here

Now take the database offline and then bring it online - the (.c, .obj, .xml, .pdb., .dll) are all gone ...

enter image description here


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.