Keep in mind this answer is from my notes from a training class ... You have to set PERMISSION_SET to EXTERNAL_ACCESS to access the server's file system or to access another server. This would make sense since you are using System. DirectoryServices to access another server (the domain controller).
PERMISSION_SET = UNSAFE allows even more access than EXTERNAL_ACCESS, actually. – NetRat Mar 25 at 5:21.
I think System. DirectoryServices assembly is simply not supported inside SQL Server. SQL Server does only allow a very specific (hardcoded) list of assemblies (SQL Server 2005, SQL Server 2008) to be used, in order to not jeopardize it's stability.
Having said that, there seems to be a way to achieve it anyway see this question/answer (haven't tried it).
Finally, I found the workaround. I added the reference to the System. DirectoryServices to the assembly that is linked to the MS SQL and in the CLR procedure code create a class from this namespace.
And so System. DirectoryServices assembly became visible from the class where the main code for DS is placed.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.