sknox (10/1/2013)
Haven't had time to research SQL 2014 yet.Guessed optimistically.
Got it wrong.
Can anyone explain why this should still be around when CLR has been available to replace its functionality since 2005?
Because of performance! CLR is very dangerous: bad written code can waste cpu time and memory resource.