By now, you who have created .NET
assemblies for execution in SQL Server 2005, know about the three
permission sets used when cataloguing an assembly:
- SAFE
- EXTERNAL_ACCESS
- UNSAFE
So, for example, if you need to access things outside of the
database you assign the permission set EXTERNAL_ACCESS to the assembly.
But what about when you do not want to allow an assembly to everything
that is possible for that particular permission set? You do not want
the assembly for example to be able to do File IO, but it should be
allowed to do external data access.
... To read the complete version of this post go here, http://sqlblogcasts.com/blogs/nielsb/SQLCLR and CAS in SQL Server 2005