Teradata Perl Migration
Teradata Perl parameters are used to configure 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.
- The values of db-bteq-tag-name and db-tdsql-tag-name in the following table can be changed.
|
Parameter |
Description |
Value Range |
Default Value |
Example |
||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Scripts to be processed in Perl files. BTEQ: Only the scripts under the BTEQ tag are processed. |
|
bteq |
db-bteq-tag-name=bteq |
||||||||
|
Scripts to be 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 add timing 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: The intermediate files are deleted. false: The intermediate files are not deleted. |
|
true |
remove-intermediate-files=true |
||||||||
|
Whether to migrate SQL commands assigned to Perl variables. 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 commands from Perl variables and migrate them. true: SQL commands assigned to Perl variables are migrated. false: The Perl variables with SQL commands are skipped during migration. Example 1: (The parameter is true) Input:
Output:
Example 2: Input
Output
|
|
true |
migrate-variables=true |
||||||||
|
Level of Perl migration logs. error: Only errors are logged. warning: Errors and warnings are logged. info: Errors, warnings, and information are logged. This level contains all information. |
|
info |
logging-level=info |
||||||||
|
Maximum number of log files that can be 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:
After the archiving, a new log file perlDSC.log with a timestamp is generated. |
1MB - 10MB |
5MB |
log-file-size=10MB |
||||||||
|
Whether to migrate execute_query that contains SQL content. true: The query is migrated. false: The query is not migrated. Example: (This parameter is true) Input:
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