To extract data from a source, first define sources in the repository. You can import or create the following types of source definitions in the Source Analyzer:
You can import sources that use multibyte character sets. Source code pages must be a superset of the target code pages.
Source definitions can be single- or multi-group. A single-group source has a single group in the source definition. Relational sources use a single-group source definition. A multi-group source has multiple groups in the source definition. Non-relational sources such as XML sources use multi-group source definitions.
Note:Because source definitions must match the source, you should import definitions instead of creating them manually.
Special Character Handling in Source Definitions
You can import, create, or edit source definitions with table and column names containing special characters, such as the slash (/) character through the Designer. When you use the Source Analyzer to import a source definition, the Designer retains special characters in table and field names.
However, when you add a source definition with special characters to a mapping, the Designer either retains or replaces the special character. Also, when you generate the default SQL statement in a Source Qualifier transformation for a relational source, the Designer uses quotation marks around some special characters. The Designer handles special characters differently for relational and non-relational sources.
The following table describes how the Designer handles special characters in relational sources:
Note:Although the Designer replaces slash characters with underscore characters for source table names, it retains slash characters in source definition port names.
The following table describes how the Designer handles special characters in non-relational sources:
Some databases require special configuration or commands to allow table and field names containing the slash character. For more information, see the database documentation.
Updating Source Definitions
When you update a source definition, the Designer propagates the changes to all mappings using that source. Some changes to source definitions can invalidate mappings.
The following table describes how you can impact mappings when you edit source definitions:
When you add a new column to a source in the Source Analyzer, all mappings using the source definition remain valid. However, when you add a new column and change some of its properties, the Designer invalidates mappings using the source definition.
You can change the following properties for a newly added source column without invalidating a mapping:
If the changes invalidate the mapping, you must open and edit the mapping. Then click Repository > Save to save the changes to the repository. If the invalidated mapping is used in a session, you must validate the session.
When you create a session, you can specify a source location different from the location you use when you import the source definition. If the source is a file, you can override some of the file properties when you create a session.
Using The Designer
Working With Sources
Working With Flat Files
Working With Targets
Mapping Parameters And Variables
Working With User-defined Functions
Using The Debugger
Viewing Data Lineage
Managing Business Components
Creating Cubes And Dimensions
Using The Mapping Wizards
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.