SQL Server Home
Thank you for your feedback!
Unable to truncate memory optimized table
- by Muhammad.Imran
as By Design
The product team believes this item works according to its intended design.
A more detailed explanation for the resolution of this particular item may have been provided in the comments section.
7/14/2013 7:37:10 AM
This issue is related to memory optimized table once you try to truncate it.
ATTACH A FILE
EDIT THIS ITEM
Item can only be reassigned when it is active.
to post a comment.
Please enter a comment.
[MSFT] on 10/27/2013 at 10:58 PM
Correct, the delete will log all the rows so subsequently, the size of log will be larger. Since logging for in-memory table is more efficient (i.e. we combine multiple log records into 1) + no index rows are logged, the impact of logging will not be as severe as for disk-based tables. Trucnate table is something we will consider in the next release
on 10/18/2013 at 7:40 PM
I agree that there is a need for TRUNCATE support. It is cumbersome to have to implement/maintain different scripts etc. based on the type of the table.
Also, is there a LOG file issue with DELETE vs TRUNCATE?
on 8/7/2013 at 10:41 AM
delete take too long if we use DURABILITY = SCHEMA_AND_DATA
i think you should implement TRUNCATE TABLE.
[MSFT] on 7/15/2013 at 9:54 AM
Thanks for this feedback.
The feature TRUNCATE TABLE is not supported with memory-optimized tables in SQL2014. You can use DELETE FROM instead.
Jos de Bruijn
Program Manager - SQL Server Database Systems
to post a workaround.
Please enter a workaround.
Attach a file
© 2016 Microsoft