Do what I say, not what I do with CLR Triggers

Yesterday, I blogged and posted some code regarding CLR Triggers.  One thing to be careful of is the use of the SqlPipe object.  I am using it for debugging purposes.  Don't put a bunch of SqlPipe outputs to your application in your CLR objects.  You may break things inadvertently.  I should have commented in my code that the SqlPipe statements were for debugging purposes only.  Typically, for objects that don't have a user interface, I like to write to the event log, but I found the SqlPipe to be so easy and gave me immediate output that I used it.  I don't think I would do this in a production application.

Wally