blocks|key|1595421|text|问得好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1595422|如果数据传输量很大？您是否正在处理多个数据文件并需要事务(在文件系统级和数据库级)？您是否正在处理位于不同位置的多个数据源(例如ftp、本地文件系统、数据库)？|1595423|如果上面的答案是肯定的，那么继续使用ssis。基本上，对于小型数据导入/导出作业，.net是很酷的，但是当您有更复杂的任务时，ssis无疑是赢家。|1595424|我考虑的另一件事是-当ssis中的一切都可用时，编写.net代码是否值得。(不要误会我-我喜欢编码)然而，你编码的任何东西，你都需要维护:-)|1595425|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

good question. 

if the amount of data transfer huge? are you processing multiple data files and need transactions (both at file system level and database level)? are you dealing with multiple data sources at different locations (for eg ftp, local file system, database)?

if answers to above are yes then go ahead with ssis. basically .net is cool with small data import / export jobs, but when you have anything more complex, ssis is a definite winner

the other thing which i look at is - is it worth writing .net code when everything is available inside ssis. (dont mistake me - i love coding) however, anything you code, you need to maintain :-)

blocks|key|1380375|text|我想这取决于你在做什么。SSIS非常强大，就像旧的DTS一样。如果你正在加载很多项目，并且希望有不断的变化，我会一直使用SSIS。如果你只想加载几个项目，而且它是为很多客户准备的，我会把它放在代码中。我更喜欢在内部ETL过程中使用SSIS，但是当我需要将数据从遗留系统加载到SQL数据库中时，我会在客户端使用.Net。现在，正如我之前所说的，如果你有很多转换和许多不同的数据竖井要加载，我认为你会疯狂地在.Net中这样做，我会选择SSIS。如果你只有几个项目要加载，而且它是针对单个应用程序的，并且可能会作为应用程序的一部分安装在不同的客户端，那么我会一直使用.Net。就我的两分钱。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1380376|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I guess it depends on what you are doing. SSIS is very powerful, just like old DTS. If you are loading lots of items and expect to have constant change, I would go SSIS all the way. If you are looking to load only a few items and it’s for lots of customers, I would put it in code. I prefer SSIS for in house ETL processes, but I use .Net at client shops when I need to load data from a legacy system into a SQL database. Now as I stated before if you have a lot of transformations and lots of different data silos to load, I think you would be crazy to do this in .Net and I would go SSIS. If you have only a few items to load and it’s for a single application and may be installed as part of an application at various clients, I would go .Net all the way. Just my 2 cents.

blocks|key|1595484|text|SSIS有许多内置的方法，可以从不同的数据源进行转换，您可以将它们串在一起，使其非常可定制。他们内置了优化，使他们的速度更快。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1595485|您还可以使用.NET进行自己的自定义转换，以利用SSIS作业的速度和可重复性。|1595486|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

SSIS has many built in ways of doing transformations from different data sources and you can string them together in a way that makes it very customizeable. They have built in optimizations that make them fast.

You can also use .NET to make your own custom transformations to take advantage of the speed and repeatability of an SSIS job.

blocks|key|1380470|text|我认为项目时间/预算限制和标准工具的使用是使用SSIS的一些最大的理由。在大多数情况下，创建一个SSIS包比尝试用.NET编写类似的代码要快得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1380471|但话虽如此，SSIS似乎有很多pain+points，有时可能会使这一论点无效。当我开发一个需要在许多不同客户端的不同环境中运行的解决方案时，我就是这样做的。我在项目中评估的越多，SSIS看起来就越痛苦。架构合理的.NET解决方案更容易部署，更可靠，更灵活，更容易理解，而且还可以实现非常好的性能。|offset|length|1380472|IMHO:考虑对只需要部署到一个或两个内部SQL+Server环境的项目使用SSIS。否则，.NET方法将很快变得更有吸引力。|1380473|entityMap|0|LINK|mutability|MUTABLE|url|http://ayende.com/Blog/archive/2007/07/15/SSIS-15-Faults.aspx^0|0|F|B|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I think project time/budget constraints and the use of a standard tool are some of the biggest arguments for using SSIS. Creating an SSIS package is most of the times way faster than trying to code something similar in .NET. 

But with that said, it seems like SSIS have a lot of <a href="http://ayende.com/Blog/archive/2007/07/15/SSIS-15-Faults.aspx" rel="noreferrer">pain points</a> that sometimes might invalidate this argument. It did for me when developing a solution that needed to run in different environments at many different clients. SSIS simply looked too painful the more I evaluated it for the project. A properly architected .NET solution is easier to deploy, more reliable, more flexible, easier to understand and can also achieve very good performance. 

IMHO: consider using SSIS for projects that you only need to deploy to one or maybe two in house SQL Server environments. Otherwise, the .NET approach will quickly become more appealing.

blocks|key|1380524|text|我认为主要的优点是以可视化的方式定义整个编程结构。任何一个看过SSIS包的人都会觉得它很容易理解。与SSIS和SQL的紧密集成使您可以成为SQL的一部分，以实现备份计划和巨大的优势。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1380525|正如每个人所解释的，如果你正在做大量的数据操作，它是一个很好的工具。这是免费的，如果你有SQL，你都设置去，并与VS2008投标非常容易学习|1380526|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I think main advantage is defining the entire programming construct visually. Any one look at the SSIS package is it pretty much self explainer. The tight integration with the SSIS with SQL allows you to be part of SQL for back up scheduling and huge plus. 

As every one explained if you are doing the lot of data manipulation it is good tool. It is free if you have SQL you all set to go and very easy to learn with VS 2008 BIDS

blocks|key|1380556|text|无论人们在前面的答案中说什么都是正确的，但我认为使用SSIS而不是编码最重要的方面是拥有简单的维护过程和可重用的产品。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1380557|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Whatever folks say in previous answers are correct but I think that the most important aspect of using SSIS instead of coding is to have easy maintenance process and also a reusable product.

blocks|key|1595633|text|SSIS对于BI应用程序来说是很棒的，你可以操作阶段表上的数据，然后使DataWarehouse表上的数据可用于BI。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1595634|我可以连接到SAP，甲骨文，以获取员工信息，并在PowerBI，QlikView等上可用。|1595635|如果你知道在哪里和为什么使用它，这是一个很好的工具。使用ir，因为它很酷，你会有麻烦。|1595636|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

SSIS is great for BI applications, you can manipulate the data on Stage Table and than make avaiable on DataWarehouse tables to be used for BI. 

I can connect on SAP, Oracle to get employee information and make avaiable on PowerBI, QlikView, etc...

Its a nice tool if you know where and why use it. Use ir because its cool you will have troubles.

blocks|key|1380625|text|顾名思义，SSIS是一个集成系统。在.net中，很难处理到不同数据源的连接器，例如excel、teradata、oracle等，也很难履行责任，优雅地关闭这些连接，垃圾收集，处理内存问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1380626|因此，SSIS是开箱即用的产品，非常适合这样的场景:不仅需要从两个不同的源提取数据，而且在将数据写入目标位置(无论是sql服务器、平面文件或其他数据库系统)之前，还需要执行一系列查找、转换、合并、派生和计算。|1380627|SSIS也有检查点，如果包由于任何原因而失败，它将从它停止的地方恢复(它需要配置，因为这不是默认行为)。|1380628|此外，SSIS将为您节省大量时间，因为它的任务是可重用的，并且其部署过程非常容易实现和调度，并由出色的事件处理提供支持。|1380629|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

As the name suggests, SSIS is an integration system. It can be very difficult in .net to handle connectors to disparate data sources such as excel, teradata, oracle etc and also to live up to the responsibility to gracefully close those connections, garbage collection, handling memory issues.

So, SSIS is out of the box product perfect for scenarios where data not only needs to be pulled from, say, two different sources, but then a series lookups, transformations, merges, derivations and calculations need to be performed before writing it to a target location(be it sql server, a flat file or another db system). 

SSIS also has checkpoints where, if the package fails due to any reason, it will pick up from where it left off (it needs to be configured as this is not default behavior).

In addition, SSIS will save you a lot of time because its tasks are reusable and its deployment process is fairly easy to implement and schedule, supported by great event handling.

blocks|key|1380675|text|基本上，SSIS有许多优点，如将数据从A点到B点的传输分成较小的块，并分别在其中进行调试，能够轻松地访问SQL+Server表，处理XML数据，使用c#脚本调用API并将数据保存在数据库中，读取数据库数据和远程服务器上的FTP等等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1380676|除了一堆已经存在的BI块之外，您还可以使用自己的参数和输出创建自己的自定义任务。|1380677|希望我能够在已经存在的答案中添加一些要点。|1380678|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Basically SSIS has many advantages like splitting data transfer from point A to point B in smaller blocks and debug them in individually, able to access SQL Server Tables easily, work on XML data, API calls using c# scripts and saving data on DB, Read DB data and FTP on remote server and many more.
 
Apart from bunch of already existing BI blocks, you can also create your own customized tasks with its own parameters and outputs.
 
Hope I was able to add some points to the already existing answers.

blocks|key|1380744|text|SSIS通常用于ETL+(提取转换加载)。具体的使用案例是SSAS+(SQL+Server+Analysis+Services)多维数据集的预处理；以及使用数据更改捕获的增强提取。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1380745|它可以执行典型的自动化操作，包括FTP和电子邮件。还有使用脚本任务(C#或Visual+Basic)的编程方面，因此SSIS具有它所包含的控件之外的功能……|1380746|可以将包编程为使用条件控制流路径。例如，周一到周五完成某项任务，周六和周日完成不同的任务。如果某些条件不满足，则拒绝执行ETL。|1380747|SSIS包可以调用其他SSIS包。这使代码保持模块化，允许重用。|1380748|它可以处理各种数据源，并使用派生列控件执行简单的转换。这与在源服务器(例如，可能是Oracle或Hadoop+-您无法使用本地SQL+server控制的服务器)上进行转换相比。|1380749|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

SSIS is generally used for ETL (Extract Transform Load). Specific use cases are the pre-processing of SSAS (SQL Server Analysis Services) cubes; and enhanced extraction using Data Change Capture.

It can do typical automation, including FTP, and email. There is the programming aspect using script-tasks (C# or Visual Basic), so SSIS has functionality beyond it's included controls...

Packages can be programmed to use conditional control-flow path. For example, do a certain task Monday thru Friday, and a different task Saturday &amp; Sundays. Or refuse to perform ETL if certain conditions are not met.

SSIS packages can call other SSIS packages. That keeps the code modular, allowing re-use.

It can work with various Data Sources, and perform simple transformation using the Derived Column control. This is versus doing transformation on the source server (which could be Oracle or Hadoop for example- something you don't have control of with your local SQL Server).

If I have the option of using <code>.Net</code> and can do data <code>transformations</code> just fine in .Net, when would I need <code>SSIS</code>? Is there a certain task that <code>SSIS</code> would be better for? Are the added benefits of transparency worth it? Is it just what I am more comfortable with? What are the best practices for determining this?

.Net vs SSIS: What should SSIS be used for?

文件系统

SQL数据库

SQL Server

数据库

服务器

Hadoop 

如果我可以选择使用.Net，并且可以在.Net中很好地执行data transformations，那么我什么时候需要SSIS？有没有特定的任务是SSIS更适合的？透明带来的额外好处值得吗？这只是我觉得更舒服的吗？确定这一点的最佳实践是什么？

问.Net与SSIS: SSIS应该用来做什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.Net与SSIS: SSIS应该用来做什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.Net与SSIS: SSIS应该用来做什么？
EN