RE: SQL CLR permissions needed after deployment to target server (

Thanks.

Not really sure which group this type of question should be posted in, since
it covers both programming and security.

"Charles Wang[MSFT]" wrote:

Hi,

Thank you for posting here!

I notice that you have posted the same question in our
microsoft.public.sqlserver. programming newsgroup, which I have already
responded. So please check my answer there and if you need any further
assistance on this particular issue, please reply to me in that thread so I
can follow up with you in time.

For your convenience, I have included my reply as follows:

------------------
I understand that you encounter the permission issue when you run your CLR
assemblies on your server side.
If I have misunderstood, please let me know.

It seemed that EXTERNAL_ACCESS was not granted to your assembly. I
recommend that you try setting your database to trustworthy and then
elevate the PERMISSION_SET of your assembly to EXTERNAL_ACCESS, such as:
ALTER DATABASE YourDatabaseName SET TRUSTWORTHY ON
Go
ALTER ASSEMBLY YourAssemblyName WITH PERMISSION_SET = EXTERNAL_ACCESS
Go

Also I would like to let you know that the current assembly
System.Data.SqlClient is not a supported assembly for SQL Server. Please
carefully test it to see if there is any issue after you deploy it. You may
refer to this KB article:
Support policy for untested .NET Framework assemblies in the SQL Server
2005 CLR-hosted environment
http://support.microsoft.com/default.aspx?scid=kb;EN-US;922672


Hope this helps. Please feel free to let me know if you have any other
questions or concerns.
------------------

Thank you and have a nice day!


Best regards,
Charles Wang
Microsoft Online Community Support

======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================


.

Relevant Pages

  • Re: "We Never Use Assembly Language"
    ... especially about efficiency of programming with Assembly. ... in all those Assemblies in order to have it merged in the official ... Its pity that Linux cannot offer something like RosAsm. ...
    (alt.lang.asm)
  • RE: SQL CLR permissions needed after deployment to target server (not
    ... Support policy for untested .NET Framework assemblies in the SQL Server ... When responding to posts, ...
    (microsoft.public.sqlserver.security)
  • Re: Programmed device - labelling requirements?
    ... >point at a document saying "thou shall label all programmed devices ... >How does industry cope with batch programming and labelling at a latter ... generated and a new complete build configuration documentation (and ... While there are only a few assemblies that are under ...
    (sci.electronics.design)
  • Re: Is it possiable
    ... You can develop even with Notepad if you want to, and compile ... The programming ease which IDEs offer save you much time, ... You can still compile your assemblies from the command-line, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: 2008 Upgrade Testing
    ... retrieval/rebuild of parts and assemblies from old versions? ... You know it's going to be slower. ... Since we don't do any programming, our main test is to open up the parts ...
    (comp.cad.solidworks)