Don t Say I Didn t Warn You

Don't Say I Didn't Warn You

Have you guessed yet that I'm not completely thrilled with CLR database procedures?

I urge you to be cautious in implementing CLR database procedures. You want to create lasting solutions, but the jury is still out on CLR. It is new and exciting and presents many opportunities for ingenious solutions, but because it is new, it is also bound to change. If you overuse them (simply because you can), you leave yourself (or the database developer who comes after you) open to a nightmare rewrite.

Transact-SQL is here to stay. It is a safer choice, and it is a better choice for data access and set operations than managed code. Even managed code reverts to Transact-SQL for data access, so there's really no point in re-inventing the wheel in these situations.