External database accounts external-accounts

Create your external account and select External database as your external account’s Type and Amazon Redshift as Provider type.

Click Create.

To configure the Amazon Redshift external account, fill in the following fields:

• Type: Amazon Redshift

• Server: Enter the DNS name of your Redshift server.

• Account: Provide the Redshift username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Database: Specify the database name if it is not already defined in the DSN. Leave this field empty if the DSN includes the database.

• Working schema: Input the schema name where Adobe Campaign will operate.

• Options: Add any advanced configuration options that may be required by your environment.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Redshift database. Once these functions are available, click Deploy functions to activate them.

Link your Storage account to optimize performance and enable faster data-loading processes between Adobe Campaign and Amazon Redshift.

Enter your Account role which determines the permissions Adobe Campaign will use when interacting with your Redshift environment.

Create your external account and select External database as your external account’s Type and Amazon Redshift (legacy) as Provider type.

Click Create.

To configure the Amazon Redshift (legacy) external account, fill in the following fields:

• Type: Amazon Redshift (legacy)

• Server: Enter the DNS name of your Redshift server.

• Account: Provide the Redshift username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Database: Specify the database name if it is not already defined in the DSN. Leave this field empty if the DSN includes the database.

• Working schema: Input the schema name where Adobe Campaign will operate.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Redshift database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and Amazon Redshift as Provider type.

Click Create.

To configure the Azure Synapse Analytics external account, fill in the following fields:

• Type: Azure Synapse Analytics

• Server: Enter the URL of the Azure Synapse server.

• Account: Provide the username that will authenticate with the Synapse database.

• Password: Enter the password associated with the account.

• Database: Specify the target database you want Adobe Campaign to connect to.

• Tables and functions prefix: By default, this is set to the account name. You may adjust it if you prefer to use a different prefix for identifying Campaign-related objects.

• Options: Add any advanced configuration options that may be required by your environment.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

You can choose to enable the Use a work tablespace for tables option, then specify the Tablespace of tables where your working tables will be stored.

If needed, enable the Use a work tablespace for indexes option, then provide the Indexes tablespace.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Azure Synapse Analytics database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and Databricks as Provider type.

Click Create.

To configure the Databricks external account, fill in the following fields:

• Type: Databricks

• Server: Enter the DNS name of your Databricks server.

• Account: Provide the Databricks username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Catalog: Specify the catalog you want to use.

• Working schema: Enter the name of the schema where Adobe Campaign will create and manage its working objects.

• Options: Add any advanced configuration options that may be required by your environment.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Databricks database. Once these functions are available, click Deploy functions to activate them.

Link your Storage account to optimize performance and enable faster data-loading processes between Adobe Campaign and Databricks.

Create your external account and select External database as your external account’s Type and Google BigQuery as Provider type.

Click Create.

To configure the Google BigQuery external account, fill in the following fields:

• Type: Google BigQuery

• Account: Enter the username or service account that Adobe Campaign will use to connect to BigQuery.

• Login file upload method: Choose how to provide the service account keym either by entering the key file path manually or by uploading the key file directly to the server.

• Server: If you select the manual entry option, provide the server URL.

• Project: Specify the Google Cloud project ID associated with your BigQuery instance.

• Dataset: Enter the name of the dataset where Adobe Campaign will store and query data.

• Options: Add any advanced configuration options that may be required by your environment.

Under Parameters, paste the contents of the service account key JSON file to authenticate Adobe Campaign with Google BigQuery.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Google BigQuery database. Once these functions are available, click Deploy functions to activate them.

If your environment requires proxy access to connect to the BigQuery server, configure the proxy settings.

Start by selecting your proxy type: http, http_no_tunnel, socks4, or socks5.

Fill in the following proxy configuration fields to establish secure access:

• Proxy Host: The address of the proxy server.
• Proxy Port: The port used by the proxy server.
• Proxy UID: The user ID for authenticating with the proxy server, if required.
• Proxy Host: The password corresponding to the Proxy UID (if applicable).

Create your external account and select External database as your external account’s Type and Microsoft SQL Server as Provider type.

Click Create.

To configure the Microsoft SQL Server external account, fill in the following fields:

• Type: Microsoft SQL Server

• Server: Enter the DNS name of your Microsoft SQL Server.

• Account: Provide the Microsoft SQL Server username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Database: Specify the database name if it is not already defined in the DSN. Leave this field empty if the DSN includes the database.

• Options: Add any advanced configuration options that may be required by your environment.

• Tables and functions prefix: By default, this is set to the account name. You may adjust it if you prefer to use a different prefix for identifying Campaign-related objects.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

You can choose to enable the Use a work tablespace for tables option, then specify the Tablespace of tables where your working tables will be stored.

If needed, enable the Use a work tablespace for indexes option, then provide the Indexes tablespace.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Microsoft SQL Server database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and MySQL as Provider type.

Click Create.

To configure the MySQL external account, fill in the following fields:

• Type: MySQL

• Server: Enter the DNS name of your MySQL server.

• Account: Provide the MySQL username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Database: Specify the database name if it is not already defined in the DSN. Leave this field empty if the DSN includes the database.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

You can choose to enable the Use a work tablespace for tables option, then specify the Tablespace of tables where your working tables will be stored.

If needed, enable the Use a work tablespace for indexes option, then provide the Indexes tablespace.

After setting up the connection, create the Adobe Campaign SQL functions in your remote MySQL database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and Netezza as Provider type.

Click Create.

To configure the Netezza external account, fill in the following fields:

• Type: Netezza

• Server: Enter the DNS name of your Netezza server.

• Account: Provide the Netezza username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Database: Specify the database name if it is not already defined in the DSN. Leave this field empty if the DSN includes the database.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

You can choose to enable the Use a work tablespace for tables option, then specify the Tablespace of tables where your working tables will be stored.

If needed, enable the Use a work tablespace for indexes option, then provide the Indexes tablespace.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Netezza database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and ODBC (Sybase ASE, Sybase IQ) as Provider type.

Click Create.

To configure the ODBC (Sybase ASE, Sybase IQ) external account, fill in the following fields:

• Type: ODBC (Sybase ASE, Sybase IQ)

• Server: Enter the DNS name of your ODBC (Sybase ASE, Sybase IQ) server.

• Account: Provide the ODBC (Sybase ASE, Sybase IQ) Server username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Database: Specify the database name if it is not already defined in the DSN. Leave this field empty if the DSN includes the database.

• Options: Add any advanced configuration options that may be required by your environment.

• Mass insert tool: Specify the full path to the mass insertion tool executable.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

You can choose to enable the Use a work tablespace for tables option, then specify the Tablespace of tables where your working tables will be stored.

If needed, enable the Use a work tablespace for indexes option, then provide the Indexes tablespace.

After setting up the connection, create the Adobe Campaign SQL functions in your remote ODBC database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and Amazon Redshift as Provider type.

Click Create.

To configure the HTTP relay to remote database external account, fill in the following fields:

• Type: HTTP relay to remote database

• Server: Enter the full URL of the HTTP relay server that connects to your remote database.

• Account: Provide the username used to authenticate with the HTTP relay server.

• Password: Enter the password associated with this account.

• Datasource: Specify the target database to which Adobe Campaign should connect through the relay.

• Options: Add any advanced configuration options that may be required by your environment.

You can choose to enable the Use a work tablespace for tables option, then specify the Tablespace of tables where your working tables will be stored.

If needed, enable the Use a work tablespace for indexes option, then provide the Indexes tablespace.

After setting up the connection, create the Adobe Campaign SQL functions in your remote HTTP relay to remote database database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and Oracle as Provider type.

Click Create.

To configure the Oracle external account, fill in the following fields:

• Type: Oracle

• Server: Enter the DNS name of your Oracle server.

• Account: Provide the Oracle username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

You can choose to enable the Use a work tablespace for tables option, then specify the Tablespace of tables where your working tables will be stored.

If needed, enable the Use a work tablespace for indexes option, then provide the Indexes tablespace.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Oracle database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and PostgreSQL as Provider type.

Click Create.

To configure the PostgreSQL external account, fill in the following fields:

• Type: PostgreSQL

• Server: Enter the DNS name of your PostgreSQL server.

• Account: Provide the PostgreSQL username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Database: Specify the database name if it is not already defined in the DSN. Leave this field empty if the DSN includes the database.

• Working schema: Enter the name of the schema where Adobe Campaign will create and manage its working objects.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

You can choose to enable the Use a work tablespace for tables option, then specify the Tablespace of tables where your working tables will be stored.

If needed, enable the Use a work tablespace for indexes option, then provide the Indexes tablespace.

After setting up the connection, create the Adobe Campaign SQL functions in your remote PostgreSQL database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and SAP HANA as Provider type.

Click Create.

To configure the SAP HANA external account, fill in the following fields:

• Type: SAP HANA

• Server: Enter the DNS name of your SAP HANA server.

• Account: Provide the SAP HANA username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Options: Add any advanced configuration options that may be required by your environment.

• Working schema: Enter the name of the schema where Adobe Campaign will create and manage its working objects.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

You can choose to enable the Use a work tablespace for tables option, then specify the Tablespace of tables where your working tables will be stored.

If needed, enable the Use a work tablespace for indexes option, then provide the Indexes tablespace.

After setting up the connection, create the Adobe Campaign SQL functions in your remote SAP HANA database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and Snowflake as Provider type.

Click Create.

To configure the Snowflake external account, fill in the following fields:

• Type: Snowflake

• Server: Enter the DNS name of your Snowflake server.

• Account: Provide the Snowflake username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Database: Specify the database name if it is not already defined in the DSN. Leave this field empty if the DSN includes the database.

• Working schema: Enter the name of the schema where Adobe Campaign will create and manage its working objects.

• Options: Add any advanced configuration options that may be required by your environment.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Snowflake database. Once these functions are available, click Deploy functions to activate them.

If you are using key pair authentication, from the keypair.auth menu, enter the required values for:

• Password: The passphrase protecting the private key, if applicable.

• Private key: The private key used to authenticate the Snowflake account.

Create your external account and select External database as your external account’s Type and Teradata as Provider type.

Click Create.

To configure the Teradata external account, fill in the following fields:

• Type: Teradata

• Server: Enter the DNS name of your Teradata server.

• Account: Provide the Teradata username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Database: Specify the database name if it is not already defined in the DSN. Leave this field empty if the DSN includes the database.

• Options: Add any advanced configuration options that may be required by your environment.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

You can choose to enable the Use a work tablespace for tables option, then specify the Tablespace of tables where your working tables will be stored.

If needed, enable the Use a work tablespace for indexes option, then provide the Indexes tablespace.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Teradata database. Once these functions are available, click Deploy functions to activate them.

If needed, enter your PostConnect Script if you want a script to execute automatically after each connection is established. If you want the script to run every time, enable the Run every time option.

Create your external account and select External database as your external account’s Type and Vertica Analytics as Provider type.

Click Create.

To configure the Vertica Analytics external account, fill in the following fields:

• Type: Vertica Analytics

• Server: Enter the DNS name of your Vertica Analytics server.

• Account: Provide the Vertica Analytics username that will be used for authentication.

• Password: Enter the password associated with the user account.

• Database: Specify the database name if it is not already defined in the DSN. Leave this field empty if the DSN includes the database.

• Working schema: Enter the name of the schema where Adobe Campaign will create and manage its working objects.

• Options: Add any advanced configuration options that may be required by your environment.

• Time zone: Select or enter the server’s time zone to ensure accurate time-based operations.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Vertica Analytics database. Once these functions are available, click Deploy functions to activate them.

Create your external account and select External database as your external account’s Type and Microsoft Fabric as Provider type.

Click Create.

To configure the Microsoft Fabric external account, fill in the following fields:

• Type: Microsoft Fabric

• Server: Enter the DNS name of your Microsoft Fabric server.

• Account: Provide the Microsoft Fabric username (or service principal) that will be used for authentication.

• Password: Enter the password or secret associated with the account.

• Options: Add any advanced configuration options that may be required by your environment.

After setting up the connection, create the Adobe Campaign SQL functions in your remote Redshift database. Once these functions are available, click Deploy functions to activate them.

Link your Storage account to optimize performance and enable faster data-loading processes between Adobe Campaign and Microsoft Fabric.

Enter your Account role which determines the permissions Adobe Campaign will use when interacting with your Redshift environment.