SQL scripts by data source

Use separate SQL scripts to create views or materialized views for each data source.

The following table provides information about the scripts that you must generate for each data source, the resulting script name, and the scripts that must be run against the IBM® EMM application database for creating views or materialized views:
Note:
  • The table lists the default names for the data sources and the generated scripts, which you might have changed.
  • The Interact reporting schemas reference more than one data source. Generate a separate SQL script for each data source.
Table 1. SQL scripts by data source

This three-columned table provides information about the reporting schema in one column, data source (default names) in the second column, and the script name (default names).
Reporting schema Data source (default names) Script name (default names)

All Campaign reporting schemas

Campaign system tables

(campaignPartition1DS)

Campaign.sql, unless you generated separate scripts for each reporting schema. If you did, each script is named after the individual schema.

eMessage Mailing Performance

eMessage tracking tables, which are with the Campaign system tables

(campaignPartition1DS)

eMessage_Mailing_ Performance.sql

Interact Deployment History, Interact Performance, and Interact Views

Interact design time database

(campaignPartition1DS)

Interact.sql

Interact Learning

Interact Learning tables

(InteractLearningDS)

Interact_Learning.sql

Interact Run Time

Interact run time database

(InteractRTDS)

Interact_Runtime.sql