Starting with SQL Server 2017, the CLR strict security advanced setting is enabled by default. For more information, see https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/CLR-strict-security.
To successfully install Integrity or migrate your Integrity databases on SQL Server 2017 or later, disable CLR strict security. After installing Integrity, you can enable CLR strict security if it is required for your environment.
To disable or enable CLR strict security:
-
Open Microsoft SQL Server Management Studio.
-
Connect to the SQL Server.
-
Run the following commands to disable CLR strict security:
EXEC sp_configure 'show advanced options', 1;
RECONFIGURE;
EXEC sp_configure 'CLR strict security', 0;
RECONFIGURE;
EXEC sp_configure 'show advanced options', 0;
RECONFIGURE; -
After you install Integrity or migrate your Integrity databases, enable CLR strict security, if desired, by running the following commands:
EXEC sp_configure 'show advanced options', 1;
RECONFIGURE;
EXEC sp_configure 'CLR strict security', 1;
RECONFIGURE;
EXEC sp_configure 'show advanced options', 0;
RECONFIGURE;
Cost Threshold
The Cost Threshold for Parallelism option in SQL Server specifies the threshold at which SQL Server creates and runs parallel plans for queries. To prevent the query from using too many threads, you should update this value in SQL Server Management Studio.
To change the Cost Threshold for Parallelism value:
-
Open Microsoft SQL Server Management Studio.
-
Connect to the SQL Server.
-
Right-click on the SQL Server, and then click Properties. The Server Properties window is displayed.
-
In the left pane, click Advanced.
-
In the right pane under Parallelism, change the value for Cost Threshold for Parallelism to 50. The default value is 5.