I have a AFTER INSERT/UPDATE trigger on a table in TempDB (to be explained further down)
which does not fire/execute when a record is inserted or updated from "applications".
However, when I go into SSMS and update a record I can watch it execute in a profiler trace without error.
Is there any obvious reason for this I am overlooking ?
Google has not been my friend so far on this search....
This is a local application running SQLEXPRESS and using tempdb for speed due to many, many singluar and batch INSERTS.
I tried/and thought maybe something to do with creating the trigger "with execute as owner" but that does not seem to be the issue.
Additionally - the trigger is doing an INSERT/UPDATE into a table in another database (same instance) - again, this works fine if I execute it in SSMS.
In this scenario - I happen to be logged into SSMS and the database as domain\administrator - and the application is running as that user as well.
My assumption being, for testing - that indeed both processes are running as same user, eliminating permissions as the reason....