title: Can a trigger be forced to run in a separate context than the user in SQL Server 2000?
body: <p>Let's say I have a SQL Server 2000 table, any name will do, it's irrelevant for this topic.  On this table I have a trigger that runs after update or insert.</p>
  
  <p>The user is able to insert and update the table on which the trigger is attached, but not on other tables that the trigger targets.</p>
  
  <p>If the user modifies data in the original table, I get an exception complaining that the user doesn't have permission to modify data in the target tables of the trigger.</p>
  
  <p>I assume this is caused by the fact that the trigger is running in the context of the user.  Is there a way to have the trigger run in its own context or am I not interpreting the cause of this exception correctly?</p>
  
  <p><strong>Edit:</strong> I should point out that I'm using SQL Server 2000, so using EXECUTE AS won't work.</p>