Appropriate Use of SQL CLR
I am looking for advise on appropriate use of SQL CLR. I had initially hoped that I could expose certain functions from assemblies of a fairly extensive application for use in SQL functions and stored procedures. The number of unsafe assemblies that I am having to register to do that makes me think it's a bad idea.
Should SQL CLR be thought of as just an alternative to T-SQL when implementing something in SQL is difficult or impractical?
[457 byte] By [
FPowell] at [2007-11-11 10:14:02]
