sqlclr

I have been researching SQL Server CLR UDFs and parallelism for some time. The general consensus seems to be that in SQL Server 2008 and later, a scalar value CLR UDF with DataAccessKind.None should allow parallel execution. However, when I use my scalar value UDF in my view in SQL Server 2012, it still kills parallel execution in joins and the like. Is there something special I need to add to my C# code or the T-SQL UDF definition to indicate that it is safe for parallel execution? Thanks. According to the MSDN forum that is linked to in the first comment on the question, your C# code roughly

I have written an assembly which is integrated in sql server, providing some stored procedures written in C#. The assembly has a readonly static variable holding some configuration data. This data is manipulated via stored procedures, which are also provided by the assembly. Obviously I have to synchronize access to this static variable. I tried to use lock(someGuard) { // ... access static configuration } inside my configuration class. But then I get a HostProtectionException, telling me, that the assembly has to run with full trust to do that. Is there a better way to do that? There is

I get the following errors in my development database: A .NET Framework error occurred during execution of user-defined routine or aggregate "SpCreateTable": System.Security.HostProtectionException: Attempted to perform an operation that was forbidden by the CLR host. The protected resources (only available with full trust) were: All The demanded resources were: Synchronization, ExternalThreading Is the correct solution to set trustworthy = on? What are security concerns with this? The TRUSTWORTHY property of a database (when set to ON ) essentially declares to SQL Server that code contained

I am developping an SQL Server Database Project in Visual Studio which is in fact a User Defined Function. In this project, I included Json.NET as a reference (using NuGet). I managed to publish (and make work) my assembly and the UDF to my SQL Server instance by first turning the database TRUSTWORTHY ON (since my project is UNSAFE) and then running this: CREATE ASSEMBLY [System.Runtime.Serialization] FROM 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Runtime.Serialization.dll' WITH PERMISSION_SET = UNSAFE; Which turns out to be an assembly Json.NET depends on (if I don't do it, I get

I have been struggling with a SQL Server CLR stored procedure. Background: We are using SQL Server 2014 and a CLR stored procedure has been implemented which calls a customer's web service. The threading was initially used not to slow the main thread of SQL Server CLR. Although, now, I know that using threading under CLR is no best idea, it has been working correctly for 6 years (since SQL Server 2008). It has been migrated to SQL Server 2014 recently. The problem On my development machine, same as on test system we have no problem with the solution. On the customer system, the thread, which

I've already dived into SQL clr programming. Unfortunately my first attempt is troubled. My C# assembly code is just so: enter code here public partial class FirstCLRRoutines { public static int GetCLRFrameworkMajorVersion() { return System.Environment.Version.Major; } } And SQL code is: USE master GO CREATE ASSEMBLY [Chapter2.FirstCLRRoutine] FROM 'D:\projeler\SQL_CLR\SQL_CLR\bin\Debug\SQL_CLR.dll' But I get this error message from MSSMSE: Msg 6218, Level 16, State 3, Line 1 CREATE ASSEMBLY for assembly 'SQL_CLR' failed because assembly 'SQL_CLR' failed verification. Check if the referenced