Although SQLCLR has great power I think it is very important to tell the reader that it also brings MANY undesirable things in.

- Bad Exception handling is just one of the examples.

- Bad routines could cause stability problems even knowing that is a "hosted" CLR

- There is a very high risk of introducing code that is not Server-Side friendly.

- Problems caused by CLR objects are a lot harder to deal with.