DocumentationCampaignCampaign Classic v7 Documentation
v7
Applies to Campaign Classic v7 only

Configure access to Snowflake configure-access-to-snowflake

Last update: Thu Nov 23 2023 00:00:00 GMT+0000 (Coordinated Universal Time)

Use Campaign Federated Data Access (FDA) option to process information stored in an external database. Follow the steps below to configure access to Snowflake.

  1. Configure Snowflake on Linux.
  2. Configure the Snowflake external account in Campaign
NOTE
Snowflake connector is available for hosted and on-premise deployments. For more on this, refer to this page.

Snowflake on Linux snowflake-linux

To configure Snowflake on Linux, follow the steps below:

  1. Before the ODBC installation, check that the following packages are installed on your Linux distribution:

    • For Red Hat/CentOS:

      code language-none 
      yum update
yum upgrade
yum install -y grep sed tar wget perl curl

    • For Debian:

      code language-none 
      apt-get update
apt-get upgrade
apt-get install -y grep sed tar wget perl curl

  2. Before running the script, you can have access to more information with the --help option:

    code language-none 
    cd /usr/local/neolane/nl6/bin/fda-setup-scripts/
./snowflake_odbc-setup.sh --help

  3. Access the directory where the script is located and run the following script as a root user:

    code language-none 
    cd /usr/local/neolane/nl6/bin/fda-setup-scripts
./snowflake_odbc-setup.sh

  4. After installing the ODBC drivers, you need to restart Campaign Classic. To do so, run the following command:

    code language-none 
    systemctl stop nlserver.service
systemctl start nlserver.service

  5. In Campaign, you can then configure your Snowflake external account. For more on how to configure your external account, refer to this section.

Snowflake external account snowflake-external

You need to create a Snowflake external account to connect your Campaign instance to your Snowflake external database.

  1. From Campaign Explorer, click Administration ‘>’ Platform ‘>’ External accounts.

  2. Click New.

  3. Select External database as your external account’s Type.

  4. Under Configuration, select Snowflake from the Type drop-down.

  5. Add your Server URL and Database.

  6. Configure the Snowflake external account authentication:

    • For Account/password authentication, you must specify:

      • Account: Name of the user

      • Password: User account password.

    • For Keypair authentication, click the Keypair Auth tab to use your Private key to authenticate and copy paste your Private key.

  7. Click the Parameters tab then the Deploy functions button to create functions.

    note note
    NOTE
    For all functions to be available, you need to create the Adobe Campaign SQL functions in the remote database. For more information, refer to this page.

  8. Click Save when your configuration is finished.

The connector supports the following options:

Option
Description
workschema
Database schema to use for work tables
warehouse
Name of the default warehouse to use. It will override the user’s default.
TimeZoneName
By default empty, which means that the system time zone of the Campaign Classic app server is used. The option can be used to force the TIMEZONE session parameter.
For more on this, refer to this page.
WeekStart
WEEK_START session parameter. By default set to 0.
For more on this, refer to this page.
UseCachedResult
USE_CACHED_RESULTS session parameter. By default set to TRUE. This option can be used to disable Snowflake cached results.
For more on this, refer to this page.
bulkThreads
Number of threads to use for Snowflake bulk-loader, more threads mean a better performance for bigger bulk-loads. By default set to 1. The number can be adjusted, depending on the machine thread count.
chunkSize
Determines the file size of the bulk-loader chunk. By default set to 128MB. Can be modified for a more optimal performance, when used with bulkThreads. More concurrently active threads mean better performance.
For more on this, refer to Snowflake documentation.
StageName
Name of the pre-provisioned internal stage. It will be used in bulk load instead of creating a new temporary stage.
recommendation-more-help
601d79c3-e613-4db3-889a-ae959cd9e3e1