CLR Stored Procedures and Deploying them to a Client [modified]
-
About 5 months ago when I was designing a database for a client, a co-worker wrote a number of CLR stored procedures that augment functionality of my database. The database was delivered to the client, and we have since found out that one of the stored procedures has a habit of throwing a DivideByZero exception in ceratin cases. I have fixed the code and redeployed it locally, but I'm having problems understanding how I get it to the client when I don't have direct deployment access to their SQL server. Do I need to copy a .dll and manually move it to the client, or is there a way I need to set things up(even if only temporarily) so that I can deploy the new CLR code to the remove server? Thanks in advance. -- modified at 14:14 Wednesday 5th July, 2006 Forgot to mention, I've generated scripts using these instructions: http://msdn2.microsoft.com/en-us/library/ms345099.aspx[^], but they refuse to let me drop and then add the CLR's (as I do with other items). I'm using all of the defaults in the wizard, is there something I can check to remove the constraint check briefly so I can remove something and add a new version in its place? Alternately, can I alter the statement that is being generated? ALTER ASSEMBLY [Assembly Name] ADD FILE FROM (huge hex code) AS N'filename.cs' Should the Add be modify?
-
About 5 months ago when I was designing a database for a client, a co-worker wrote a number of CLR stored procedures that augment functionality of my database. The database was delivered to the client, and we have since found out that one of the stored procedures has a habit of throwing a DivideByZero exception in ceratin cases. I have fixed the code and redeployed it locally, but I'm having problems understanding how I get it to the client when I don't have direct deployment access to their SQL server. Do I need to copy a .dll and manually move it to the client, or is there a way I need to set things up(even if only temporarily) so that I can deploy the new CLR code to the remove server? Thanks in advance. -- modified at 14:14 Wednesday 5th July, 2006 Forgot to mention, I've generated scripts using these instructions: http://msdn2.microsoft.com/en-us/library/ms345099.aspx[^], but they refuse to let me drop and then add the CLR's (as I do with other items). I'm using all of the defaults in the wizard, is there something I can check to remove the constraint check briefly so I can remove something and add a new version in its place? Alternately, can I alter the statement that is being generated? ALTER ASSEMBLY [Assembly Name] ADD FILE FROM (huge hex code) AS N'filename.cs' Should the Add be modify?
Figured out my issue. Since I had a number of stored procedures and functions, I needed to perform a massive drop and add (drop sp, drop fun, drop assem, add assem, add fun, add sp), but that appears to have successfully transfered them over. The msdn link above is really helpful for generating those files, but I think they probably need to include a paragraph or so about dealing with dependencies.