DTS，SSIS，Informatica，PL/SQL脚本 [英] DTS vs. SSIS vs. Informatica vs. PL/SQL Scripting
问题描述
过去，我曾使用Informatica进行某些ETL(提取转换加载)，但发现它运行缓慢，通常将其替换为某些PL/SQL脚本(当时使用的是Oracle).
In the past, I have used Informatica for some ETL (Extraction Transformation Loading) but found it rather slow and usually replaced it with some PL/SQL scripts (was using Oracle at the time).
(根据答案中的反馈修改问题)
(questions revised based on feedback in answers)
我认为DTS在SSIS之前是Microsoft的ETL工具.
I gather that DTS was Microsoft's ETL tool prior to SSIS.
- 使用DTS将现有应用程序转换为SSIS会很困难吗?
- 鉴于SSIS是Microsoft工具，并且与SQL Server紧密集成(实际上是SQL Server的一部分)，使用它是否有任何弊端?我看不到任何效率问题，因为我想您可以在SSIS中做任何事情，而就ETL而言，您可以没有它.
推荐答案
我相信 SSIS 是当今的Microsoft ETL工具，代替了DTS.
I believe SSIS is Microsoft's ETL tool today, replacing DTS.
重要的是要记住，ETL性能与您的模式，如何进行传输以及与工具一样重要.例如，如果您有索引，它们的运行速度将比批量传输并在完成后创建索引的速度慢.如果您一次执行大量操作，则将创建回滚日志，该回滚日志会增加大小并减慢该过程的速度.较小的批次可能会运行得更快，因为回滚日志不必那么大.
It's important to remember that ETL performance has as much to do with your schema and how you're doing the transfer as it does the tool. For example, if you've got indexes they'll run slower than if you do a bulk transfer and create the indexes after it's done. If you do a large batch all at once you're creating rollback logs that increase in size and slow the process down. It could be that smaller batches will run faster, because the rollback log doesn't have to be as big.
不要屈服于膝盖，不要责怪工具.仔细查看您的操作方式，以确保您不会摔倒自己.
Don't give in to the knee-jerk reaction and blame the tool. Look critically at how you're doing it to make sure that you're not shooting yourself in the foot.
这篇关于DTS，SSIS，Informatica，PL/SQL脚本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
