>Just logging to another file should not be causing the SQL server to hang if run in-process, and why do you need a dll for it ? C# coded complex biz logic ? As there are a few possible failure points, either bracket the action in a transaction or make it two step with a field on the newly inserted record which gets flipped to "logged" after the write to special file has been verified. Are you just confronting a BOH-spawned DBA ? Why should a little function create so much havoc ?


>Or are you trying to set up a pattern usable for hordes of rookie programmers ?

I like that! :)