To be clear, I'm not a hater of SQLCLR. And I don't hate what you wrote in your good article as SQLCLR. But...
I've had quite the opposite experience with SQLCLR triggers for audit tables. Someone copied a bunch of them to multiple tables (they were generic and would work on any table you copied them to). For tables with (way to) many columns, it was taking more than 4 minutes to update just 4 columns on just 10,000 rows. I know I'm slipping but after I converted them to T-SQL, they generally took less than 400 milliseconds.
If I had sent out the database with those original SQLCLR triggers on them, then I have had thousands pissed off customers. 😉
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems
Create a Tally Function (fnTally)