Some options can be used multiple times if applicable, e.g. connection.cast MyDatabase1="MICROSOFT SQL SERVER" Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g. Negation can be defined with the preceding dash character (e.g. The condition must be escaped with double quotes if it contains any spaces inside (e.g. ![]() Multiple conditions can be defined by using a space as a separator (e.g. Use regular expressions in java format if needed (e.g. Specify a search filter for the sub directories. The directory of Teradata TPT scripts to import. the metadata backup if available (can be set in the Miscellaneous parameter with -backup option, although this common option is not implemented on all bridges for technical reasons). the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6) Refer to the current general known limitations at or bundled in Documentation/ReadMe/MIMBKnownLimitations.html How do I reference my current vairable name, instead of having to its name(s)?Ī: Any undefined variable value is the actual variable name (striped out of any special characters if present). Q: My parameterized variables are my only script source and I do not want to edit their variable names. database schema, tables, columns) as well as the Data Integration (DI/ETL/ELT) models for the data flow lineage between these data stores. This bridge parses Teradata Parallel Transporter (TPT) scripts to extract the data models of their source and target data stores (e.g. Metadata: Multi-Model, Data Store (Physical Data Model), (Source and Target Data Stores, Transformation Lineage, Expression Parsing) ![]() Tool: Teradata / Teradata Database version 12.x to 17.x via TPT File File Multi-Model, Data Store (Physical Data Model), (Source and Target Data Stores, Transformation Lineage, Expression Parsing) via TPT File File
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |