The Server Edition of Softadmin requires the use of CLR SQL assemblies.
By default, CLR integration is disabled in SQL Server. To enable it, you must activate CLR support and grant the Softadmin assembly permission to execute.
Run the following commands to enable CLR integration:
EXEC sp_configure 'show advanced options', 1;
RECONFIGURE;
EXEC sp_configure 'clr enabled', 1;
RECONFIGURE;
While the Softadmin CLR SQL assembly is developed to use the SAFE permission level, from SQL Server 2017 onward, additional steps are required to allow it to run.
There are three ways to do this:
This method allows SQL Server to trust the Softadmin assemblies, which are signed with a known public key, without granting permissions to other assemblies.
This only needs to be done once per server, even if there are multiple Softadmin systems on the same SQL Server instance.
Download the Softadmin public key and place it in a directory the SQL Server instance has read access to.
USE master;
GO
CREATE ASYMMETRIC KEY SoftadminSQL
FROM FILE = 'C:\Path\To\SoftadminPublic.snk';
CREATE LOGIN SoftadminSQL
FROM ASYMMETRIC KEY SoftadminSQL;
GRANT UNSAFE ASSEMBLY TO SoftadminSQL;
This method allows all CLR assemblies to run.
This only needs to be done once per server, even if there are multiple Softadmin systems on the same SQL Server instance.
EXEC sp_configure 'clr strict security', 0;
RECONFIGURE;
Avoid using the TRUSTWORTHY
setting to enable CLR support. It elevates the database's ability to execute code with server-level permissions, introducing significant security risks.
If the database is already marked as TRUSTWORTHY
for other reasons, CLR assemblies may run without additional configuration. This is a side effect of the setting, not a recommended practice.