Enabling CLR in SQL Server 2005

Discussion in 'Databases' started by AlanK, Aug 25, 2006.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. AlanK

    AlanK

    I have written my stored procedures , triggers and User defined functions using Managed code.

    I have been able to deploy the assemblies to my database within Discountasp.net

    In order to execute them I nned to run them I need to enable CLR

    exec sp_configure "clr enabled",1
    RECONFIGURE

    I do not have permissions . How to we Accomplish this?
     
    AlanK, Aug 25, 2006
    #1
  2. Takeshi Eto

    Takeshi Eto DiscountASP.NET Staff

    Takeshi Eto, Aug 25, 2006
    #2
  3. AlanK

    AlanK

    Well that answer was very dissappointing. This is one of the most significant enhancementsin Sql Server 2005 . Do you think you will be supporting it in the near future??
     
    AlanK, Aug 25, 2006
    #3
  4. Takeshi Eto

    Takeshi Eto DiscountASP.NET Staff

    Takeshi Eto, Aug 25, 2006
    #4
  5. Bruce

    Bruce DiscountASP.NET Staff

    Yeah.. SQL 2k5 do not have the proper resource segragation and permission sandboxing like IIS does. What this means is a problematic CLR can easily crash the server.


    Before SQL 2k5 was officially launched, we tested a putting some bad code into the CLR and made a call to it using SQL. It completely hung SQL and crashed the process.


    I reflected this problem to the SQL team engineer beforeSQL 2k5 was launched, the response was that SQL was designed tobe anEnterprise database (mostly used in Corporate) andnot much designconsideration was given tohostingin a shared environment.





    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
    Bruce, Aug 25, 2006
    #5
  6. joelnet

    joelnet

    our policyis derived frominternal testing and performance, not product documentation or articles.


    Joel Thoms
    DiscountASP.NET
    http://www.DiscountASP.NET
     
    joelnet, Sep 6, 2006
    #6
  7. jyjohnson

    jyjohnson

    Can you reconsider this policy? A quick Google search returned many articles that state the following:



    SQLCLR code can?t do anything more in a database than an equivalent T-SQL code module running under the same security context.

    and


     
    jyjohnson, Sep 6, 2006
    #7
  8. jyjohnson

    jyjohnson

    And that is a good policy. Except in this case there are 2 problems with it:

    1. According to Bruce the testing was on pre-release/beta software -- "Before SQL 2k5 was officially launched...". I hope you agree with me that technical policy should not be based on beta software!

    2. It sounds like once you all make a decision you will never re-consider it. Service packs and other "new information" (yes, that *should* include docs & articles) can solve/prevent problems, etc. {I know service packs can cause new problems, but my point is still valid}.

    Just my $0.02.
     
    jyjohnson, Sep 7, 2006
    #8
  9. Takeshi Eto

    Takeshi Eto DiscountASP.NET Staff

    We are always working on ways to innovate our hosting product and so we do a lot of R&D work. We tested SQL 2005 in the beta stage and we continue to do R&D work on the official version. We also keep up to date on service packs ...etc.

    If we should see an opportunity to differentiate our hosting service without degrading our customer's service, we would certainly consider it and most probably launch it.

    Eric
    DiscountASP.NET
    http://www.DiscountASP.NET
     
    Takeshi Eto, Sep 7, 2006
    #9
  10. Bruce

    Bruce DiscountASP.NET Staff

    we confirmed the same problem w/ the released version of SQL2k5.


    ie. if it runs great, no problem. If someone upload some bad code into the SQL server, it can easily use up all the server resource.


    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
    Bruce, Sep 7, 2006
    #10
  11. jyjohnson

    jyjohnson

    Ok. Thanks for trying it on the released version.
     
    jyjohnson, Sep 7, 2006
    #11
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page