Teradata SQL Configuration
Teradata parameters are used to customize rules for Teradata script migration.
Parameter |
Description |
Value Range |
Default Value |
Example |
---|---|---|---|---|
|
Rule for migrating DELETE statements without a WHERE clause. true: enables the migration of DELETE to TRUNCATE. false: disables the migration of DELETE to TRUNCATE. |
|
false |
deleteToTruncate=true |
|
Which columns specified in the primary index will be used for data distribution across nodes in the cluster. one: Data is distributed based on the first column specified in the primary index. many: Data is distributed based on all the columns specified in the primary index. This function is addressed by using the DISTRIBUTE BY clause.
NOTE:
This parameter is set to one in V100R002C60 because this version does not support multiple columns in the DISTRIBUTE BY clause. |
|
many |
distributeByHash =many |
|
This parameter is used to enable or disable Group By (grouping sets/cube/rollup) migration. true: enables the migration of GROUP BY(). false: disables the migration of GROUP BY(). |
|
false |
extendedGroupByClause=false |
|
This parameter can be used to enable and disable query optimization from IN/NOT IN to EXISTS/NOT EXISTS. |
|
false |
inToExists=false |
|
Whether to convert row-store tables to column-store tables. If this parameter is set to true, all row-store tables are converted to column-store tables during script migration. |
|
false |
rowstoreToColumnstore=false |
|
Default table type (SET/MULTISET) for CREATE TABLE. Teradata: The default table type is SET. ANSI: The default table type is MULTISET. |
|
Teradata |
session_mode=ANSI |
|
Whether to enable the migration of ALIAS. true: enables the migration of ALIAS. false: disables the migration of ALIAS. |
|
false |
tdMigrateALIAS=true |
|
Whether to enable the migration of static objects whose name starts with a dollar sign ($). This parameter is not applicable to dynamic objects, in format of ${}. true: Enclose the name of a static object with double quotation marks ("). false: Disable the migration of static objects.
NOTE:
For details, see Object name starting with $. |
|
true |
tdMigrateDOLLAR=true |
|
Whether to enable the migration of queries with the LOCK keyword. true: enables the migration of such queries and comments out the LOCK keyword. false: disables the migration of such queries. DSC Migration Tool skips this query and logs the following information: Gauss does not have equivalent syntax for LOCK option in CREATE VIEW and INSERT statement. Please enable the config_param tdMigrateLockOption to comment the LOCK syntax in the statement.
NOTE:
For details, see ACCESS LOCK. |
|
false |
tdMigrateLOCKoption=true |
|
Whether to enable the migration of ZEROIFNULL(). true: enables the migration of NULLIFZERO(). false: disables the migration of NULLIFZERO(). |
|
true |
tdMigrateNullIFZero=true |
|
Whether to enable the migration of views containing CHECK OPTION. true: comments out such views during migration. If this parameter is set to false, such views are not migrated. The tool will copy the query as it is and record the following message: Gauss does not support WITH CHECK OPTION in CREATE VIEW. Please enable the config_param tdMigrateViewCheckOption to comment the WITH CHECK OPTION syntax in the statement. |
|
false |
tdMigrateVIEWCHECKOPTION=true |
|
Whether to enable the migration of ZEROIFNULL. true: enables the migration of ZEROIFNULL(). false: disables the migration of ZEROIFNULL(). |
|
true |
tdMigrateZEROIFNULL=true |
|
Type of tables whose data is specific to a session and is stored only for the session. When the session ends, the data and tables are deleted. A volatile table can be a Migrating Tables table or an unlogged table.
NOTE:
unlogged is supported in V100R002C60 and local temporary is not. |
|
local temporary |
volatile=unlogged |
|
Whether to enable the migration of CHARACTER SET and CASESPECIFIC. true: comments out CHARACTER SET and CASESPECIFIC during script migration. false: disables the migration of CHARACTER SET and DSC. In this case, DSC copies CHARACTER SET, CASESPECIFIC and logs the following information with query details (such as the file name and statement position): Gauss does not have an equivalent syntax for CHARACTER SET & CASE SPECIFIC option in column-level. You can rewrite this statement or set the configuration parameter tdMigrateCharsetCase to TRUE to comment the Character set & Case specific syntax in this statement. |
|
false |
tdMigrateCharsetCase=false
NOTE:
If tdminatecharsetcase is set to true, comment out the special keyword of the character. |
|
Specifies whether the Teradata command line tool can be migrated. The following options are supported:
|
|
true |
terdataUtilities=true |
|
Specifies whether unique indexes can be created for column-store tables. |
|
true |
unique_primary_index_in_column_table=true |
|
Specifies whether default_charset can be migrated. The following options are supported:
|
|
LATIN |
default_charset=LATIN |
|
mergeImplementation has the following two types:
The following options are supported:
|
|
None |
mergeImplementation=None |
|
Specifies whether dsql is supported. The following options are supported:
|
|
false |
dsqlSupport=false |
|
Whether to remove column names that contain double quotes during migration. The following options are supported:
|
|
false |
tdcolumnInSensitive=false |
|
Specifies the migration mode of the CASE_N for partitioning. Gauss does not support multilevel (nested) partitioning: The following options are supported:
|
|
comment |
tdMigrateCASE_N=comment |
|
Specifies the migration mode of the RANGE_N for partitioning. Gauss does not support multilevel (nested) partitioning: The following options are supported:
|
|
range |
tdMigrateRANGE_N=range |
|
Specifies whether addMonth can be migrated. The following options are supported:
If this parameter is set to true, ADD_MONTHS changes into mig_td_ext.ADD_MONTHS (added mig_td_ext) after the migration. Otherwise, migration is not supported. |
|
false |
tdMigrateAddMonth=false |
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