扩展存储过程
With Yukon on the horizon, I'm thinking about the "unmanaged Yukon equivalent" we have now - Extended Stored Procedures. I've used them in the past for such cleverness as calling out to Ws Services from within SQL Server and calling back to other boxes in an asychronous Observer-Observable pattern to let folks know about Data Changing for cache clearing events.
随着育空的到来,我正在考虑我们现在拥有的“等同于育空的不受管理”的产品-扩展存储过程。 过去,我曾经使用过它们,例如从SQL Server中调用Ws Services并以异步的Observer-Observable模式调用其他框,以使人们了解用于缓存清除事件的数据更改。
Now, no doubt Yukon will be much more robust even hosting in-proc componentry via Application Domains or out of proc via an ASP_WP style worker process, but until then, are Extended Stored Procedures (in VB6 and C++) evil? See http://tinyurl.com/4er4 (Google Groups Post)
现在,毫无疑问,Yukon甚至通过应用程序域托管进程内组件或通过ASP_WP样式工作者进程托管proc组件,都将更加健壮,但是在那之前,扩展存储过程(在VB6和C ++中)是邪恶的吗? 参见http://tinyurl.com/4er4(Google网上论坛帖子)
翻译自: https://www.hanselman.com/blog/extended-stored-procedures-considered-harmful
扩展存储过程