Home Dashboard Directory Help

Unable to remove filestream file and corresponding Hekaton filegroup by Hrair K


 as Won't Fix Help for as Won't Fix

Sign in
to vote
Type: Bug
ID: 800207
Opened: 9/10/2013 10:43:48 PM
Access Restriction: Public
User(s) can reproduce this bug


If you create a filestream data file and a corresponding memory optimized filegroup, then create a Hekaton table in the database with a single row, then drop the Hekaton table so there are no more memory optimized objects taking up space in memory and in the database, you will not be able to remove the filestream data file and it's corresponding memory optimized filegroup. This is important, because it was decided on later in the POC project to have the ability to create database snapshots on the database, however it's not compatible with Hektaon. Thus, in the process of removing these specialized file/filegroup, we came across this potential bug.

As additional information, I also ran the following two queries below. They both returned results (with positive KB usage values) associated to object_id's that have a negative value, these objects do not exist in the database:

select object_name(object_id), * from sys.dm_db_xtp_table_memory_stats
select object_name(object_id), * from sys.dm_db_xtp_memory_consumers
Sign in to post a comment.
Posted by Microsoft on 9/13/2013 at 9:17 AM
thanks. I am closing it

Posted by Hrair K on 9/12/2013 at 9:44 PM
Thanks for the input Sunil. I just started the process of rebuilding the database without the Hekaton filegroup. We can close this out.
Posted by Microsoft on 9/12/2013 at 12:47 PM
Harry, thanks for reporting this. In SQL14, you can't remove memory-optimized filegroup. The only option is to drop the database. While this certainly is an issue when you are doing the POCs or playing with Hekaton but we believe it will not be concern in producion because customers will either deploy with Hekaton or not. This is something we are planning to support post SQL Server 14

Please let us know if you see a neeed when you will need to drop memory-optimized filgroup is production environment

Sign in to post a workaround.