Informatica:
A data intergration tool is the best
way to indicate Informatica.
·
Informatica facilitates
a default function to export , transfer and loada large amount of data.
·
The integeration/ETL
tool in Informatica Powercenter is useful in getting the data from different
sources and can migrate or load that data into different targets .
·
Informatica tool cannot store anything or any data at all. The data can
just be moved from one place to another and that’s the reason the tool is
designed to make it capable to communicate to variety of databases and modify
data formats accordingly. Usually user need to transfer data while moving it
and Informatica can do that.
·
INFORMATICA
limits developer mistakes- this is the easiest way o answer . The Informatica
tools compresses all data integration
functions which are participating in moving data into to a series of
transformation objects.
Informatica over Teradata :
A MPP database with little scripting
(BTEQ) and pace in data flowing ability in a system.
1)
Metadata repository for the
organization's ETL ecosystem
Informatica jobs (sessions) can be arranged logically into worklets and workflows in folders.
Leads to an ecosystem which is simple to maintain and faster for architects and analysts to examine and grow.
2) Job monitoring and recovery -
By using using Informatica Workflow Monitor it is easy to keep a eye on the jobs .
Informatica jobs (sessions) can be arranged logically into worklets and workflows in folders.
Leads to an ecosystem which is simple to maintain and faster for architects and analysts to examine and grow.
2) Job monitoring and recovery -
By using using Informatica Workflow Monitor it is easy to keep a eye on the jobs .
Easier to find
out and recover in case of unsuccessful jobs or jobs running at slow speed.
User can restart again after a failure of a program/ step.
3) Informatica MarketPlace – To make the SDLC faster and to improvze the support of application, a one stop shop for lots of tools and accelerators is Informatica.
User can restart again after a failure of a program/ step.
3) Informatica MarketPlace – To make the SDLC faster and to improvze the support of application, a one stop shop for lots of tools and accelerators is Informatica.
4) There are numerous developers available in the market who have variety of skills and expertise in Informatica than Teradata.
5) Lots of connectors to various databases, including support for Teradata mLoad, tPump, FastLoad and Parallel Transporter in addition to the regular (and slow) ODBC drivers.
Some 'extraordinary' connectors might required to be purchased and might charge some additional cost.
For Examples - PowerExchange for FaceBook, Twitter, etc which source data from such social media sources.
6) Surrogate key generation through shared sequence generators inside Informatica could be speedy than producting them inside the database.
7) By using automated solutions the Company can change the ETL code to work with the new database quickly, accurately and efficiently just in case if company takes the decision to switch from Teradata to another solution. For Example company like Infosys can do this.
8) For processing the data in database , user can make use of pushdown optimization .
9) Informatica application has the capability to code ETL in such a way that processing load is balanced between ETL server and the database box . This phenomenon will be useful if the ETL server has a huge memory & CPU and/or is the database box is ageing to outperform the database in certain tasks.
10) Capacity to produce processes as web services
Let’s have a look of the advantages of Teradata over Informatica :
1) Cheaper (initially) - No initial ETL tool license costs (which can be significant), and lower OPEX costs as one doesn't need to pay for yearly support from Informatica Corp.
2) If all the data which is to be loaded is available as structured files , then Teradata is a good choice as this file can be processed in the database once they are loaded.
3) Less complex system – hence Teradata can be a good choice.
4)
Teradata developers or resources with good ANSI/Teradata SQL / BTEQ knowledge are
the only one that are required to build and upgrade the system.