sgmunson (2/26/2014)
The source code for the function is proprietary, and thus, unavailable. The number of rows it would apply to would be relatively small. As the only non-ETL alternative would be to decrypt a significantly larger quantity of rows, there's really no viable alternative ... especially from a performance perspective, where the alternative is known to be a serious performance problem waiting to happen.
Maybe... maybe not. There are a lot of things that people just don't know. Heh..; yeah... right now, I agree...we know nothing of your code but it wouldn't be the first time that someone thought they had code that was unbeatable for performance that got beaten with a bit of T-SQL prestidigitation. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.