>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 will have to get back with you on the first part of your questions, but you lost me at BOH-spawned. What is that??? :)

Beth
>
>>Sorry, this is the 3rd different way of trying to figure this problem out. We are running SQL Server 2005.
>> We need, when a specific table in the server has a record inserted into it, we need to make sure that that record info is written out to a special file.
>>
>>hope that makes sense.
>>Beth
>>
>>>What are you trying to do that you need to call a process from SQL Server? What version of SQL Server?
>>>
>>>>The definition as we know and need:
>>>> in process called from a trigger locks up the sql server and the server must be restarted if something goes wrong. out of process has it's own space and when something happens we would simply have to kill the process not restart sql server. I am quite sure the DBA's would not be happy with restarting the sql server every time some little problem occurs with this function.
>>>>
>>>>Thanks,
>>>>Beth