I agree that it's important to consider who may work on the code in the future. If we're talking DBA's, then what can one assume that a future DBA will know? Is it safe to assume he/she will know C#/VB.Net? Do we put the package together for a beginning DBA or one with 5 yrs, 10 yrs experience? Do we write it so the least competent DBA will be able to work on it?

I doubt it's a good idea to try some whiz-bang new technique just because you want to learn it. I like to take the middle of the road. I try to learn new techniques when they come out, but won't put them into production code until a couple of years down the road. That way, competent people will have the ability to work with it. I'm assuming a certain level of competence, of course. I will have to trust that my employer will hire someone at least as good as I am. 😉

Tom