March 26, 2020 at 12:00 am
Comments posted to this topic are about the item Still More Memory Optimized Table Limitations
March 26, 2020 at 12:32 pm
Now that is interesting
learned something today, thanks Steve (have never tried doing this before, so....)
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
March 26, 2020 at 3:17 pm
I don't currently work with too many In-Memory OLTP tables, so this is great to know! Thanks for the question, Steve.
March 26, 2020 at 4:32 pm
Glad you liked it
March 26, 2020 at 6:18 pm
Msg 5296, Level 16, State 1, Line 86
Object ID 565577053 (object ‘InMemoryHekatonTable’): The operation is not supported with
memory optimized tables. This object has been skipped and will not be processed
March 27, 2020 at 4:39 am
I don't work with memory-optimized tables so I searched the web for the answer. Two sources state that DBCC CHECKTABLE will return: "Msg 5296, Level 16, State 1, Line 86 Object ID 565577053 (object ‘InMemoryHekatonTable’): The operation is not supported with memory optimized tables. This object has been skipped and will not be processed." I have no reason not to believe it.
Ref. 1: DBCC CheckDB and CheckTable doesn’t check In-Memory OLTP.
Ref. 2: Comment 8. in Postponing Our Use of In Memory OLTP.
See also system view sys.messages.
USE master;
GO
SELECT [message_id]
,[language_id]
,[severity]
,[is_event_logged]
,[text]
FROM [master].[sys].[messages]
WHERE [message_id] = 5296 and [language_id] = 1033;
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply