tsyomatsyoma Posts: 4 Bronze 1
edited June 16, 2015 12:04PM in DLM Dashboard
I have an error when working with inmemory. For example, when UPDATE statistics
An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back.

If you write in block CATCH
     - Left intentionally blank :(
you can see the text of the error:
Msg 41317, Level 16, State 3, Procedure RG_SQLLighthouse_WriteError, Line 36
A user transaction that accesses memory optimized tables or natively compiled procedures can not access more than one user database or databases model and msdb, and it can not write to master.

The documentation says that it is necessary disable the trigger when working with inmemory but I think it is wrong.
Are there other solutions?

Sorry for my bad english


  • Thanks for bringing this to our attention. I've been able to reproduce the issue here, and I've done a quick investigation into how we might fix it.

    I've added supporting memory optimised tables to our backlog. However, given that it's a lot of work, and given that you are so far the only user that's asked for it, and also given that there are a lot of things on the backlog, I think that it's going to be a while before we work on it :(
Sign In or Register to comment.