最高效的 SSIS 虚拟组件
我经常想使用虚拟组件作为错误重定向或条件拆分的端点。 (见图)我使用它是为了在调试时查看数据集。
我通常使用多播作为虚拟组件,但很好奇它是否是最有效的组件(曾经该包投入生产)。
我可以在不运行调试时禁用该组件,但想看看是否有一个组件会更有效。
I frequently want to use a dummy component as the endpoint for either an Error Redirect or Conditional Split. (See diagram) I use this so I can view the dataset while debugging.
I normally use Multicast as the dummy component, but was curious if it was the most efficient component to use (once the package goes into production).
I could make the component disable when not running in debug, but wanted to see if there was a component that would be more efficient.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
我已经按照您描述的方式使用了多播转换,但仅用于初始调试。作为虚拟组件,它是最容易处理的。但是,我认为您无法禁用数据中存在的
数据流源
、数据流转换
或数据流目标
流程任务。我认为只能使用表达式禁用控制流任务。您可以保留多播,但在将包发布到生产环境之前您可能需要删除数据查看器。I have used Multicast transformation the way you have described but only for initial debugging. It is the most easiest to deal with as a dummy component. However, I don't think you can disable the
Data Flow Sources
,Data Flow Transformations
orData Flow Destinations
that exist within Data Flow Task. I think only the Control Flow tasks can be disabled using Expressions. You can leave the Multicast but you might want to delete the Data Viewers before you publish the package to production.我们通常使用从此处下载的 TRASH Destination:
http://www.konesans.com /products/trash-destination.aspx
We usually use the TRASH Destination that we downloaded from here:
http://www.konesans.com/products/trash-destination.aspx