Site Sections
Posts
24
Comments
14
Trackbacks
0
Tuesday, June 30, 2009
Request for the permission of type 'System.Data.SqlClient.SqlClientPermission failed Error

After some time working on another SQL CLR I am getting an error

Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=' failed.

This procedure needed to access a stored procedure on a remote server. Running that stored procedure within SQL Server Management Studio completed successfully. It just would not execute from my SQL CLR !

Doing online research did not lead to a solution.

Nearly completely tired I dropped by my DBA with this issue who decided to add SQL Account of the target SQL Server to the SQL Server box I was running this stored procedure on and bum no more issue !

posted @ Tuesday, June 30, 2009 3:09 PM | Feedback (0)
CREATE ASSEMBLY Failed Error

I was doing some new CLR Stored Procedures in SQL Server 2005 and at a certain point received error:

CREATE ASSEMBLY failed because method 'MyMethod' on type 'StoredProcedures'
in safe assembly 'MyAssembly' is storing to a static field. Storing to a static field is not allowed in safe assemblies.

Interestingly, despite all the procedures inside SQL CLR stored procedures have to be declared as static, no static fields are allowed outside them. So in my case declaring a static variable outside SqlProcedure.

[Microsoft.SqlServer.Server.SqlProcedure]

attribute caused this error.

So if you really want to share state outside stored procedures using SQL Server 2005 you will need to be creative.

In SQL Server 2008 this can be done using table variables.

posted @ Tuesday, June 30, 2009 2:59 PM | Feedback (0)
Archives
Image Galleries
Computing
News
Did you know you can create your own search engine with Google?
Twitter