Solomon, thx for your great articles about CLR.
For quite some time now I'm looking for a way to protect my CLR functions from unauthorized distribution to an arbitrary number of sql servers. Is there a possibility to bring in some sort of license into an assembly that needs to be varified and cannot be re-distributed by script?
I already thought of a license key that is stored inside the master database of the licensed server. It could be queried/validated from inside the assembly, but that would mean a horrible performance loss to the CLR functions. I didn't find any way to validate a license once and then keep it validated for it's next calls.
Does anyone have any further ideas on this?