Sep 122016
 

SQL Server 2016 supports AFTER triggers! I could find no good example of how to do this with a project I’m working on, so I figured out how to make this work. The following before and after screenshots are from a SQL Server 2016 instance and the DVDStore3 package. I modified a trigger to work with In-Memory OLTP.

BEFORE

hekaton-trigger-before

AFTER

hekaton-trigger-after

It compiles and works! Enjoy!

  One Response to “SQL Server 2016 In-Memory OLTP and After Trigger Support”

  1. […] David Klee shows that you can put an AFTER trigger on a memory-optimized table in SQL Server 2016: […]

This site uses Akismet to reduce spam. Learn how your comment data is processed.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close