title: Why Target required parameter for SQL Trigger?
body: <p>When authoring an INSERT Trigger for SQL Server 2008 Express in C#: I find that the below SqlTrigger annotation is required:</p>
  
  <pre><code>[SqlTrigger(Name = "SomeMethod", Target = TABLE_NAME, Event = "INSTEAD OF INSERT")]
  public static void SomeMethod() { ... }
  </code></pre>
  
  <p>The Target specification seems like an annoying requirement. I would like to have this trigger available to be run on a variety of tables. Is there anyway to avoid specifying the Target or maybe to override it during creation time in the SQL?</p>
  
  <p>Similar to this question:
  <a href="https://stackoverflow.com/questions/7564383/sql-clr-trigger-get-target-table-name">SQL CLR Trigger - get Target / Table name</a>
  but I want to be able to dynamically set the Target.</p>
  
  <p>My reason for exploring this, is I have some legacy code that is behaving badly. I want to be able to diagnose a problem potentially in the assembly trigger without shutting it down. Ideally, hijacking the inserts destined for it, doing some diagnostics, then passing back to the original assembly. I believe this Target parameter restricts me from doing this.</p>