Admin: Database-Specific Configuration Settings
The following configuration settings need to be considered when running RPI against specific database providers. Some settings pertain to specific providers, as evidenced in their naming; others apply across providers.
AWSPerformCOPYFromS3
AWSRedshiftDistributionStyle
AWSRetainCOPYGeneratedFilesInS3
AWSSourceS3BucketName: set as per the following: [AWS S3 ECP Name]\[Bucket name]
AzureSQLDWDistributionType
AzureSQLDWDropStatisticsOnTempTables
DatabaseInsertBatchLimit: applies at the following database providers.
Azure SQL
DB2
Google Spanner
MariaDB
SQL Server
DatabaseSpecificRetryableErrorEnabled
DB2RunStatsEnabled
DisableDatabaseObjectQualification: if set to True, when SQL is generated, database objects will not be qualified. Applies at the following database providers:
AWS RedShift
AWS RedShift Spectrum
Azure PostgreSQL
DB2
Google Spanner
Greenplum
Netezza
Oracle
PostgreSQL
GoogleBigQueryUseInformationSchema
OracleAudienceTempTablesIndexDisabled
OracleDegreeOfParallelism
OracleDMLSessionParallelismEnabled
OracleOptimizerDynamicSamplingLevel
OracleRunTableStats
OracleTempTablesParallelismEnabled
OracleTempTablesPKConstraintDisabled
OracleUseDirectPathInsert
OracleUseHashEnabled
SQLServerDisableRowLockHint
SQLServerIndexTempTables
SQLServerUseColumnStoreIndexTempTables: if set to true, a CLUSTERED COLUMNSTORE index will be created at RPI-generated temporary audience tables. The index will not be created if a temporary table contains one or more columns with the following data types:
text
ntext
xml
image
rowversion
sql_variant
CLR types (hierarchyid and spatial types)
nvarchar(max), varchar(max) and varbinary(max) (SQL Server versions not later than 13.x)
uniqueidentifier (SQL Server versions not later than 11.x)
SQLServerUseCountBig
SQLServerUseCreateTableInsert
SQLServerUseIdentityTempTables
SQLServerUseSelectIntoOverUpdate
SQLServerUseTempFlagTables
TeradataIndexTempTables
TeradataUsePrimaryIndex
TeradataUseTableCharacterSet
YellowbrickDistributionType