I understand where the refusal comes from. DBAs do not understand .NET code, and are afraid of possible security and performance impacts if allowing it on their servers. Nevertheless, from security perspective, SAFE assembly permission set is what it says: SAFE. With this permissions set, CLR code cannot do anything that SQL code would not be able to do. About performance – is all SQL code performing well?
I would like to point out that SQL CLR is around from version 2005. Counting public 2005 CTP versions, this means more than six years! Now the question is: did these DBAs learn anything in these six years? Do they plan to make any progress in their lives, or are they finished with personal development?
- Python for SQL Server Specialists Part 4: Python and SQL Server - April 24, 2018
- Python for SQL Server Specialists Part 3: Graphs and Machine Learning - April 11, 2018
- Python for SQL Server Specialists Part 2: Working with Data - March 22, 2018