why we use source qualifier transformation?
Answers were Sorted based on User's Feedback
Answer / vanitha
Source Qualifier Transformation basically converts
different data types to Informatica Compatible Data types.
The additional Feature of it to allow the developer to
override the SQL (Only while reading database sources) adds
better design in the map. [instead of having additional
Filters and Sorters].
| Is This Answer Correct ? | 69 Yes | 2 No |
Answer / manoj
source qualifier transformation represent the records that
the informatica server reads when it runs a session.
| Is This Answer Correct ? | 38 Yes | 8 No |
Answer / ankit
Source qualifier is the first transformation which reads
data from relation of FF source.
With SQ we can limit the source data or sort or aggregate
or remove the dupliate data via SQL Query.
| Is This Answer Correct ? | 27 Yes | 7 No |
Answer / pooja amhed
hi,
we use SQ trans as 1st trans due to its properties. in SQ
trans i means at the begin of extracting of data its self
we can remove duplicate ,we can filter,join,override the
query,pre and post sql querey.... in orther words we use it
to impore the performance.
| Is This Answer Correct ? | 16 Yes | 4 No |
Answer / vidya acharya
1. SOURCE QUALIFIER TRANSFORMATION represents the rows that informatica powercenter server reads from RELATIONAL or FLAT FILE SOURCE when it runs the session.
2. When relational or flat file source definition is added to the mapping, informatica server creates the SQ by default. thus, its a default transformation in informatica.
3. Any source(relational/flat file) cannot be read without using SQ as it converts the database specific datatype to informatica native datatype.
4. For relational sources, additional properties can be configured:
- join 2 or more table originating from same source
- source filter.
- number of sorted ports
- select distinct rows
- user defined join
- specify pre-sql and post-sql query
- sql override.
| Is This Answer Correct ? | 6 Yes | 0 No |
Answer / ravi kumar
This type of an active transmission. which allows to read the data from relational or flat file.
Ex: our source Or flat file is relational that session reads the data through source qualifier. so when ever our source is relational or flat file we must and should use this. with out source qualifier session cann't read the data. when it run time
| Is This Answer Correct ? | 5 Yes | 0 No |
Answer / srikanth reddy
source qualifier transformation mainly used in it converts
the data types into informatica level
| Is This Answer Correct ? | 5 Yes | 1 No |
Answer / ashok teja
SQ/T IS USED TO CONVERTS THE DATA INTO INFORMATICA
UNDERSTANDABLE FORMAT...
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / vankayalapati sankar
souce qualifies transformation we can use to reduce the perfomence tunning pupose and minimum four transformations cover in it.what are those 0ne resone two join the two table in this case we can use the joiner transfomation,secound resone filter condition applied in source filter option in source qualifier transformation in that case filter tranformation cover it.third resone distinct option we can use to dublicate records remove in that case sorter tranformation cover.fourth resone sql qerry write in sql qerry option use it.in that case lookup transformation cover
| Is This Answer Correct ? | 1 Yes | 0 No |
Whatis the difference between View and Materialized View ?
IN A MAPPING WHEN WE USE AGGRIGATER TRANSFORMATION WE WILL USE GROUP BY PORT. IF GROUPBY IS NOT SELECTED BY DEFAULT IT WILL TAKE ONLY THE LAST COLUMN WHY????
Hi I have two sources like A, B. My source A contain 10000 million records from that i need 20 attributes. My source B has also same 10000 million records from that i need only 1 attribute. By using Joiner i have to load into target? Is there any issue regarding this? if issue is there how to tune this mapping in best way?
What are the methods for creating reusable transforamtions?
In joiner, how to load Master table in Target?
What is fact table? Explain the different kinds of facts.
explain the scenario for bulk loading and the normal loading option in Informatica Work flow manager ???
Hi I have been asked several times the following questions. 1.How does one do incremnental loading 2.Scenario - You are trying to load reasonable amount of rows into the target table, and its taking a helluva lot of time.What could be the reasons? I hate to answer these tw0 , gives me nightmares to even think of it!!! 3.Tell me any complex situation you have faced( as an Informatica Developer) and how did you resolve it. 4.tell me any complex mapping that you have done. All the experienced people out there , please please, reply to these questions.
how to identify new and old values in source qualifier or any other transformations using informatica
By using joiner t/r we can join only 2 tables, SO if want join more than 2 flat files ,How can i join?
What is the difference between informatica 7.0 and 8.0?
What is the benefit of partitioning a session?