Required databases or schemas for Interact

The Interact runtime environment can require several databases to hold user and interaction data. Some of these requirements can be met by sharing your Campaign Customer (user) tables, while others require you to set up a unique data source.

Determine how many databases or schemas you must create or identify for use with the Interact runtime environment according to the requirements for each type of data that is stored. The Interact design environment requires tables that are not listed here because they are added to the database or schema that holds the Campaign system tables.

The following list provides a brief summary.

Create a database or schema to hold the Interact runtime tables. Set up a separate database or schema for each server group.

Create a database, schema, or view to hold the user Profile tables. You can use the customer profile database, which could be in the same database as your Campaign Customer (user) tables, as the Interact profile database. You might want a separate set of user profile tables for each interactive channel.

Create a database, schema, or view to hold the Test run tables. The Test run tables could be in the same database as your Campaign Customer (user) tables.

If you are using built-in learning, create a database or schema to hold the Learning tables.

If you are using cross-session response tracking, create a database or schema to hold a copy of the Campaign Contact History tables. Alternatively, instead of creating a copy, you could use the Campaign system tables database to run the cross-session response tracking scripts.