[转]Informatica vs SSIS
转自 http://blog.csdn.net/thy822/article/details/8489779
这篇文章, 我不能同意更多, 所以转在这里.
Here is my thinking after looking at both products...
First of all let me tell you what I like about informatica....
- Inbuilt tool to export mappings to Excel and Visio.... helpful to document Process.
- Reusability of sources,Targets and Mappings (In SSIS No native Reusabilty except you are using
BI xPress Package Builder)
- Inbuilt Version Control: SSIS Can give you this After Installing VSS,
SVN or other products but in Informatica it native feature to Checkout
and Checkin.
- Visibility of MetaData: you can click on any column in Pipeline and it
will show you where it originated from ... Pretty neat :)
- Scalibility Out of the box
Now let me go through some main points which will drive your purchase decision.
Trialing software and Cost:
Informatica costs you tons of money.. this is where 90% companies
drop their decision to buy it... once you buy it ...it will cost you
even more to maintain it every year so good luck with that!!! Every Dev
license will cost you money ... on the other end
Dev License of SQL Server is virtually Free ($50 per Dev Edition
License).... and Every SQL Server License comes with SSIS Server.
Trialing informatica is not easy... you wont find a place to download
it... on the other end downloading Entire BI Studio from
Microsoft is click away this itself shows me Informatica wants your all
money.... seriously why is that hard ????
Development Speed:
What I found after creating simple Work flow in Informatica takes
twice long than creating workflow in SSIS due to the fact informatica
stores Sources, targets and Mappings in seperate locations and then you
bring them all together in WorkFlow (similar as
ControlFlow in SSIS). One thing I like about this approach that
reusabily but from experience I hardly reuse Mappings (Load Customer
defined in one Workflow is rarely used in some other WorkFlow) so it
sounds like appealing feature but atleast not for me.
Informatica has too many jumps to Design WorkFlow, Session, Execute
WorkFlow and Monitor Progress all feels like I am using 3-4 different
applications... while SSIS is all in one compact window... and very
clean and Visual Debugging.
Scripting in SSIS is way more powerful than Informatica due to the
fact SSIS Script Editor is Shell of Visul Studio which gives you
BreakPoints, Watch, CallStack, Intellisense and Step By Step
Dbugging.... SSIS Scripting is C# or VB.net ... Informatica
is JAVA
Inbuilt Tasks:
SSIS has advantage of having several inbuilt task which is not
available in Informatica. But on the other end some Adapters and
Pipeline Features Impressed me in informatica including XML
Destination, XML Transformation, Upsert Capabilty, Visibility of
Metadata.
Some of my fav task in SSIS Missing in Informatica:
- ForEach Looping
- Script task
- File System task
In SSIS you can spent few hundred bucks to buy any missing
features.... e.g. SFTP/FTPS, Zip/Unzip, SecureEmail, Sharepoint,
SalesForce Adapter, Upsert Destination, XML Destination
Storage:
Informatica - Everything is stored in Central Repository (Oracle or
SQL DB)... what this means to developer ... You have nothing stored on
your machine. You have to be connected to Informatica Server all the
time. This was very frustrating coz I cant work
offline unlike SSIS.
SSIS: You can develop SSIS Packages on your local machine in
completely disconnected mode. When you ready to deploy to production it
can be stored in SQL Repository (msdb database) or can be stored on File
System.
Debugging WorkFlow and Pipeline:
SSIS has lots of ways to debug various things... using BreakPoints,
Watch Window, DataViewer . I didnt find similar features in Informatica.
Debugging WorkFlow is more difficust in Informatica compared to SSIS.
Community Support:
SSIS Community support is amzing compared to any ETL Product out
there. I didnt find a single scenario which is not blogged by community.
Se
Extensibility:
Informatica is closed system doesnt allow you to create your own
Sources and Targets and Tasks like SSIS Does... You will find lots of
Free tasks and Adapter in SSIS which can fit your custom need or you can
create your own using SSIS APIs ... but in Informatica
its impossible or atleast I never found a way to do so.
3rd Party Support:
Informatica keeps tight control what they want inside their
Products. If you need more functionality in informatica then you have to
Pay tons of Money to get few more Adapters - Called "Power Exchange Module".
With SSIS you will find plenty of 3rd party products which will fit to your custom ETL Need at low cost yet high Quality. (e.g.
TaskFactory)
Well
... Informatica was pioneer in ETL market … they came very first in the
market they dominated many fortune 500 hundred companies... But since
then MS Seriously invested
in BI Segment and current trend is MS BI is the fastest growing trend
due to many facts.
-
MS BI Attracts many Mid-Size and Smaller shops because its one stop
solution for entire BI (SQL, IS, RS and AS)... it costs several times
less than what other vendors charge.
- Feature gap is not any more issue after SQL Server 2008 Released.
-
Due to the tight budget and economy many companies going towards
reducing cost and that is another reason why MS BI is trending up.
-
MS invested significantly to prove it can scan out (multiple nodes) and
scale up (running on powerful hardware with multi processor and higer
RAM). MS Introduced Parallel
Datawarehouse and DW Fast Track to attract bigger shops.
- The biggest drawback for MS BI right is it only works on Windows Platform ...
Again dont take my word ... read this article...
http://www.informationweek.com/news/206104502
Conclusion:
MS BI is the fastest growing trend right now :) … so if you are
concerned about job market then Relax … you will find plenty of JOBS for
MS BI
[转]Informatica vs SSIS的更多相关文章
- SSIS 包部署 Package Store 后,在 IS 中可以执行,AGENT 执行却报错
可以执行 SSIS Package ,证明用 SSIS Package 的账户是可以执行成功的.SQL Server Agent 默认指定账号是 Network Service. 那么可以尝试一下将 ...
- SSIS 属性:ExecValueVariable
有些Task组件执行完成之后,会产生输出结果,称作Execution Value,例如,Execute SQL Task在执行完成之后,会返回受影响的数据行数.Task组件的Execution Val ...
- SSIS 实例——将SQL获取的信息传递到Email中
最近在为公司财务开发一个邮件通知时遇到了一个技术问题.原来我设计SSIS的是每天将ERP系统支付数据导出到财务支付平台后 Email 通知财务,然后财务到支付平台上进行支付操作.由于那个时候开发时间很 ...
- 介绍几种SSIS部署方式
介绍 如果你已经开发完一个不错的SSIS包并且能够在你的本地完美的运行,每个任务都亮起绿色的通过标志.这时为了能够让这个包处理能够在指定时间运行,你需要将其发布到一个服务器上,并做好相关配置.作为开发 ...
- informatica读取FTP文件
以下为一个完整的informatica读取ftp文件,并导入到系统中. 第一步: 通过shell脚本下载压缩包文件 /server/infa_shared/crm_prod/shell/ftpFrom ...
- SSIS 处理NULL
不同于SQL Server中NULL表示值是未知的(Unknown Value),没有数据类型,但是,在SSIS中,NULL是有数据类型的,要获取某一个NULL值,必须指定数据类型,例如,变量 Int ...
- SSIS 数据类型和类型转换
在进行ETL开发时,数据类型(Data Type)是最基础的,但也容易被忽略,楼主使用的SQL Server 版本是2012,用此博文记录,常用的SSIS数据类型和TSQL数据类型的映射.SSIS的数 ...
- SSIS Destination 组件使用Fast-Load mode出错
查看一个Package的历史Message 数据,发现 DataFlow Task 经常出错,错误信息的Description是: Description: "While reading c ...
- SSIS Design6:利用数据流
数据流利用内存来缓冲数据,并在内存中处理数据转换,由于内存的访问速度是非常快的,所以SSIS数据流转换性能是非常高效的.SSIS Engine将数据分批加载到内存中,当Data Flow将一批新的数据 ...
随机推荐
- SQL Server判断语句(IF ELSE/CASE WHEN )
1.IF ELSE 不能用在SELECT中,只能是块,比如: IF ... BEGIN ... END ELSE (注意这里没有ELSE IF,要实现只能在下面的块中用IF判断) BEGIN ... ...
- NuGet包引用依赖问题
如A包需要引用B包,然后在项目中安装A包时,自动把B包也装上. 在nuget命令行打包的时候,如果是指定项目的csproj文件进行打包的,都只能打包当前项目的dll,那么如果使用了第三方的dll而没有 ...
- 洛谷P3128 [USACO15DEC]最大流Max Flow [树链剖分]
题目描述 Farmer John has installed a new system of pipes to transport milk between the stalls in his b ...
- protected的使用注意
在c#的可访问性级别中,public和private算是最容易理解的,相反protected往往令人非常头疼.经常在网上查资料的朋友往往会发现,答案几乎都是前篇一律,不是从msdn上拷贝的就是从别人的 ...
- HDU 4223 Dynamic Programming?(最小连续子序列和的绝对值O(NlogN))
传送门 Description Dynamic Programming, short for DP, is the favorite of iSea. It is a method for solvi ...
- iOS - 如何自动播放H5中的音频
场景:iOS端设备,App页面跳转到H5产品介绍,背景音乐无法播放.(为什么不能自动播放,因该是iPhone人性化设定吧~) 加载H5用UIWebView空间: 代码: CGRect rect = s ...
- Python核心编程第三版第二章学习笔记
第二章 网络编程 1.学习笔记 2.课后习题 答案是按照自己理解和查阅资料来的,不保证正确性.如由错误欢迎指出,谢谢 1. 套接字:A network socket is an endpoint of ...
- zabbix 3.0快速安装简介(centos 6)
zabbix快速安装 系统版本:centos 6 1.yum源配置和zabbix.msyql安装 rpm -ivh http://mirrors.aliyun.com/zabbix/zabbix/3. ...
- CSS3-box-flex弹性盒布局
<!DOCTYPE html><html lang="en"><head> <meta charset="UTF-8" ...
- 【原】flux学习笔记
最近React(web/native)依旧如火如荼,相信大家都跃跃欲试,入职新公司,现在的团队也开始在React领域有所尝试. 2016年应该是React 逐渐走向成熟的一年.之前在原来公司搞不懂的问 ...