SQL Server Performance

Deploying CLR Code to production ?

Discussion in 'SQL Server 2005 CLR' started by SuryaKiran, Oct 9, 2008.

  1. SuryaKiran New Member

    Hi All,

    I am learning to use CLR coded stored procedures.
    In a nutshell I have understood that I need to write my code in C# or any other CLR Integrated language, Compile, generate a dll, Create an Assembly in Sql Server (Sys.Assemblies), and start executing the code, this is all fine for me.

    What I have missed to understand is-- Do I need to keep moving the DLL across Development and Production servers, to see to it that code is correctly deployed, or is there no need of explicitly moving the DLL?Let me know insights into this as I need to understand this to implement SQL CLR in the near future.Thanks in advance.
  2. moh_hassan20 New Member

    If you are using visual studio 2005/2008 , it will handle deployment with the server that you are connecting to, even in modifying your code.
    But, really for deplyment in mult production servers , it is best to create script that automate these procedures.
  3. SuryaKiran New Member

    Thank you for the reply, I think scrips are handy to move along servers.

Share This Page