What considerations go with SQL/CLR integration when database is live and changes are frequent?

Do not convert tsql to C# just becasue you are more comfortable with it. Databases are optimized to work best with SQL not C#. CLRs are only available to do things that SQL cannot do.

If you can do it in SQl, do it in SQL.

Do not convert tsql to C# just becasue you are more comfortable with it. Databases are optimized to work best with SQL not C#. CLRs are only available to do things that SQL cannot do.

If you can do it in SQl, do it in SQL. Do not do any more work until you have a real dev environment. Mucking around with stuff people are actually using is unprofessional and dangerous to the data and can quickly lose your customers.

It's not unprofessional if you're doing things exactly the way your boss tells you to. PS - I don't want this thread to become opinionated or I won't get an answer :) – Gabriel Dec 16 '10 at 16:09 @Gabriel: then perhaps you should ask your boss what is the interaction between VS magic and existing users. – Remus Rusanu Dec 16 '10 at 17:58.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.