New answers tagged

0

This might be a little more of a satisfactory answer. The problem was solved by initialising a Spatial function that calls a CLR assembly. After that the query works. I know that that was the issue because when I restore the database in question the problem comes back and the solution is as described above. I can call any spatial function that calls a CLR ...


3

The "memory" being referred to in the term "memory pressure" is physical RAM, not hard-drive space. What exactly are you attempting to do when you get this error? It seems that it could be due to attempting to invoke CLR code from within an sp_OA* OLE-Automation stored procedure call. That is documented in the following Microsoft forum thread: CLR ...


1

Community Wiki answer generated from a comment by the question author Found the answer. Turns out, the CLR Assembly was used in 2 different databases. Needed to make sure that both had trustworthy bit turned on. Also, it is obviously doing something other than string splitting because I needed to create the assembly as UNSAFE because it says that it can't ...


5

The difference is between CLR static methods (type_name::method()) and instance methods (instance.method()) Static methods are defined on the type itself and are generally utility methods that get everything they need to operate passed in as method parameters. Instance methods operate on an object of a particular datatype and are able to access the ...


0

Are you referring to calling SQL objects from .NET code (such as C#, VB, C++)? Or are you referring to calling .NET methods from SQL Objects? The syntax you are using is not valid MS SQL syntax. Common MS SQL Syntax is: Database.schema.Column Database.schema.Function(arg) OR schema.function Database.schema.StoredProcedure(arg/param) OR schema....


4

While waiting to hear back on a few questions that I posted in a comment on the Question, I will at least reiterate one of my questions: "What about your current stats leads you to suspect that SQLCLR usage is in any way related to performance issues?" From what I see of your output, SQLCLR is taking up very little memory. It has 110 MB of physical ram for ...


10

First off, just to be clear: SQLCLR / .NET / C# / VB.NET cannot query the database. Only T-SQL can query SQL Server. So in order for SQLCLR code to get data or interact with SQL Server in any way, it must establish a SqlConnection, like any other .NET app, and submit T-SQL, or execute a Stored Procedure. Yes, you can call a SQLCLR (whether it is C# or VB....


4

An error in the form of: Msg 10314, Level 16, State 11, Line 1 An error occurred in the Microsoft .NET Framework while trying to load assembly id #####. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the ...



Top 50 recent answers are included