Application Domains and CLR Integration Security

New: 5 December 2005

Microsoft SQL Server loads assemblies belonging to the same owner in the same application domain. By virtue of a set of assemblies running in the same application domain, assemblies are able to discover each other at execution time using the Microsoft .NET Framework reflection application programming interfaces or other means, and can call into them in late-bound fashion. Because such calls are occurring against assemblies belonging to the same owner, there are no SQL Server permissions checked for these calls. The placement scheme of assemblies in application domains is designed primarily to achieve scalability, security, and isolation goals, and can potentially change in future releases. Hence, you should not rely on finding assemblies in the same application domain through late-bound mechanisms.

See Also


CLR Integration Security

Help and Information

Getting SQL Server 2005 Assistance