Teradata Perl Configuration
Teradata Perl parameters are used to customize rules for Teradata Perl script migration.
Open the perl-migration.properties file in the config folder and set parameters in Table 1 as required.
- Parameter values are case-insensitive.
- You can modify the values of the following two parameters db-bteq-tag-name and db-tdsql-tag-name parameters in the following table:
Parameter |
Description |
Value Range |
Default |
Example |
||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Scripts to be processed in Perl files. BTEQ: Only the scripts under the BTEQ tag are processed. |
|
bteq |
db-bteq-tag-name=bteq |
||||||||
|
Only the scripts under the db-tdsql-tag-name tag are processed. SQL_LANG: Only the scripts under the SQL_LANG tag are processed. |
sql_lang |
sql_lang |
db-tdsql-tag-name=sql_lang |
||||||||
|
Whether to enable the insertion of scripts to calculate execution time. If it is enabled, the script will be added to each input file. |
|
false |
add-timing-on=true |
||||||||
|
Whether to delete the intermediate SQL file generated by the DSC after the migration is complete. The intermediate files contain the BTEQ and SQL_LANG syntax in SQL files. These files are used as input for DSC. true: deletes the intermediate files. false: does not delete the intermediate files. |
|
true |
remove-intermediate-files=true |
||||||||
|
Whether to enable the migration of Perl variables containing SQL statements. Perl files can contain Perl variables with SQL statements. These variables are executed by using the PREPARE and EXECUTE statement in Perl. DSC can extract SQL statements from Perl variables and migrate them. true: enables the migration of Perl variables containing SQL statements. false: disables the migration of Perl variables containing SQL statements. Example 1: If migrate-variables is set to true and the target table is:
Output
Example 2: Input
Output
|
|
true |
migrate-variables=true |
||||||||
|
Logging level of Teradata Perl migration log files. error: Log only errors. warning: Log errors and warnings. info: Log errors, warnings, and activity information. This level contains all log information. |
|
info |
logging-level=info |
||||||||
|
Maximum number of log files retained, including the log files in use and archived log files. If the number of log files exceeds the upper limit, the earliest files will be deleted until the new log files are successfully archived. |
3 - 10 |
5 |
log-file-count=10 |
||||||||
|
Maximum file size. Upon reaching the specified size, a file is archived by adding a timestamp to the file name. Example: perlDSC_2018-07-08_16_12_08.log After the archiving, a new log file perlDSC.log with a timestamp is generated. |
1MB - 10MB |
5MB |
log-file-size=10MB |
||||||||
|
Whether to enable the migration of execute_query containing SQL statements. true: enables the migration of execute_query containing SQL statements. false: disables the migration of execute_query containing SQL statements. The following is an example: migrate-executequery is set to true and input is as follows:
Output
|
|
true |
migrate-executequery =true |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot