Thank you very much - - Is it full of potential pitfalls, dangers, etc?
This is what I am hearing from a developer -
"Seems dangerous. I went to a talk on reliable code at the .NET
conference. The steps to make absolutely sure that all memory is
reclaimed and all resources are freed (even if you receive a thread
abort in the middle of a final statement) requires a deep understanding
of CLR and garbage collection. The talk was created because of the
ability in SQL 2005 to execute C# code within SQL server. To maintain
the '5' nines of up-time requires writing very safe code. Also, for
example, what would happen if a trigger on record insert required a hit
against a web service that happens to be timing out (let's say
30sec)? Would the record be available? Table be locked? Insert
statement throw an error? Etc."

Tom