• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2070
  • Last Modified:

.NET SQL CLR advantages/disadvantages?

In regards to debugging and deploying a .NET SQL CLR assembly, I'd like to hear comments about experiences or any links that discuss advantages/disadvantages.
  • 2
2 Solutions
Never debug on a production server. All threads can stop on a server when debugging. Debugging against a local installed database is preferred.
You have to follow a procedure to get it to work against a remote server and have to have the correct version of visual studio (pro or team-system), not express for example.

I searched the internet and found a relevant and quite correct description at: http://www.mssqltips.com/tip.asp?tip=1624
brettrAuthor Commented:

That all sounds fine for advantages but I'm looking for real world experience.  

There isn't much out there on issues with deploying and debugging an sql clr.  But I have read some about those issues and it gets very time consuming for little return.  I'd would like to know more about those issues.


I read that.  Seems like you will run into the regular hurdles with debugging on a remote machine in .NET, which is sometimes impossible on a corp network.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now