如果程序员使用SSIS，如果是这样，为什么？ [英] Should programmers use SSIS, and if so, why?
问题描述
作为一个.NET开发人员，为了什么原因，我应该更喜欢SSIS包在编写代码？我们的一吨的生产包在我目前的工作，他们是一个噩梦都写（也许是画？）和维护。每个包看起来像C＃和VB.NET脚本在那里的抽象分解点混合五彩一碗意大利面条。为了弄清每一个执行SQL任务或Foreach循环不，我要双击该死的东西，并通过文字值和表达式，分散在多个选项卡的树浏览。
As a .NET developer, for what reasons should I prefer SSIS packages over writing code? We have a ton of packages in production where I currently work, and they're a nightmare to both "write" (perhaps draw?) and maintain. Each package looks like a bowl of multicolored spaghetti with C# and VB.NET scripts mixed in at the points where the abstractions break down. To figure out what each "Execute SQL Task" or "Foreach Loop" does, I have to double click the damned thing and browse through a tree of literal values and expressions, scattered across multiple tabs.
我是开放的胸襟，所以我想知道是否有其他的优秀的开发人员的发现SSIS不仅仅是编写一些代码更富有成效。如果您发现SSIS更有效率，请告诉我为什么。
I'm open minded, so I'd like to know if any other good developers find SSIS more productive than just writing some code. If you do find SSIS more productive, please tell me why.
推荐答案
我使用SSIS每天维护和管理大型数据仓库和立方体。我已经100％的商业智能和数据仓库两年。在此之前，我是10的.NET应用程序开发人员。
I use SSIS every day to maintain and manage a large data warehouse and cube. I have been 100% business intelligence and data warehousing for two years. Before that I was a .NET application developer for 10.
SSIS的值是一个工作流引擎从一个地方移动到另一个数据也许有一些有限的转型沿途条件分支。如果你的软件包中含有大量的脚本，那么你的团队使用SSIS了错误的任务或不舒服SQL或已经购买到炒作。 SSIS包调试非常困难。脚本组件是一个绝对的噩梦和格式化应该只使用循环，或者作为最后的手段。
The value of SSIS is as a workflow engine to move data from one spot to another with maybe some limited transformation and conditional branching along the way. If your packages contain a lot of script then your team is using SSIS for the wrong tasks or isn't comfortable with SQL or has bought into the hype. SSIS packages are very difficult to debug. Script components are an absolute nightmare and should be used only for formatting, looping, or as a last resort.
- 保持你的包简单，SQL任务和数据流任务。
- 请尽可能多的工作，尽可能SSIS以外，最好是在SQL
- 保持你的变量在一个单一的全球范围内
- 保持你的SQL变量或存储过程，从来没有在网上
- 保持你的变量值在配置存储，最好是SQL数据库
- Keep your packages simple, sql tasks and data flow tasks.
- Do as much work as possible outside of SSIS, preferably in SQL
- Keep your variables in a single global scope
- Keep your SQL in variables or store procedures, never in-line
- Keep your variable values in a configuration store, preferably a SQL database
这篇关于如果程序员使用SSIS，如果是这样，为什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
