SQL Server Performance

Does anyone have a standard as to how you store the original source code for CLRs?

Discussion in 'SQL Server 2005 CLR' started by lcerni, Aug 6, 2008.

  1. lcerni New Member

    Does anyone have a standard as to how you store the original source code for CLRs? Our concern here is that a developer will have the source code on his desk top and then leaves the company. Thus, the original source code gets lost on his PC never to be found. It appears that this source code does not resided anywhere in the database like a procedure. Unless the more experience people know something that I don't know. Currently, we do not have a repository for this source code. What do you do if you need to make a change and recompile it (and the original programmer has left)? Do you have the developers store the code in a directory somewhere? We don’t have change management here. We really don't have any standards in place. I am currently trying to put some in. I am wondering what others are doing. I am wondering what others have as a process for storing the original code for CLRs.
  2. satya Moderator

    Its a standard policy we follow that to save the code on server side (non-sql for CLR procedures) and using versioning tool to validate the code segment.
  3. lcerni New Member

    Which versioning tool do you use? Is it a free one? I have research the various versioning tools because obviously I would like one but unfortunately it doesn't fit into the company's budget.

Share This Page