what is Partitioning ? where we can use Partition?
- 2 Answers
- 22457 Views
- IBM, TCS, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / mahesh
The Partitioning Option increases Power Center?s
performance through parallel data processing, and this
option provides a thread-based architecture and automatic
data partitioning that optimizes parallel processing on
multiprocessor and grid-based hardware environments.
Partitions are used to optimize the session performance. We
can select in session properties for partitions
Types- Default----pass through partition, key range
partition, round robin partition, hash partition.
| Is This Answer Correct ? | 28 Yes | 5 No |
Answer / annu
Partitioning is a utility provided by informatica which
evolves nature of parallel processing on a grid or
multiprocessor database architecture. Partition means
a "thread of ETL data load in chunks". Like Unix, Multiple
data load thead will be executed parallely and sync up the
result set to one instance of Target.
For more detail of using Informatica Partitioning with
visual graphs
visit : http://informatica-tech-talk.blogspot.com/
| Is This Answer Correct ? | 4 Yes | 0 No |
Briefly explain the aggregator transformation?
what is Partitioning ? where we can use Partition?
tell me 5 session failure in real time how can you solve that in your project?
If we have lookup table in workflow how do you trouble shhot to increase performance?
What is CDC? How to implement CDC?
In indirect file loading, suppose we have less no.of flat files then we can enter files names manually in list file creation. If millions of files are there, how can we enter the flat file names in list file?
What are the types of lookup transformation?
Scenario is like this: Name Sal A 10; B 20; C 30; Then Output should be Name Sal A 10; B 20; C 30; Total 60; Use SQL For this scenario
Suppose we have a source qualifier transformation that populates two target tables. How do you ensure tgt2 is loaded after tgt1?
how u know when to use a static cache and dynamic cache in lookup transformation.
Explain the aggregator transformation?
Can we use the mapping parameters or variables created in one mapping into any other reusable transformation?
Teradata 
