Overview
DWA uses several schemas to organize and maintain your data warehouse. Typically, there is a schema for each integration you enable. Additionally, there are several KORE-created schemas used for data modeling, reporting, and internal processing. You can only read data from these schemas, not write (except for custom).
Integration schemas
When you enable an integration, DWA extracts data from the vendor and stores it in your data warehouse. Each integration has its own schema within the warehouse. The schema name usually matches the vendor's name but may sometimes differ for historical reasons; the integration's documentation will provide the schema name in those cases. If you have multiple accounts with a vendor (such as Facebook or YouTube), there may be a separate schema for each account with a suffix applied to each schema's name.
Custom schema
The custom schema allows you to directly write data into DWA, enabling you to import static data from any source which you can then use in your reports and queries.
Data modeling and Golden Record schemas
KORE uses three schemas for data modeling:
dwa— Ticketing data modelkore— KORE Data Modelkorebi— Archtics ticket coding (supplements the Ticketing data model)
If your organization creates Golden Records using Helix or the Insights Portal, those records will be stored in the helix or insights schema respectively.
Other schemas
When a DWA integration pulls in new data, KORE may use these schemas during the ETL (extract, transform, load) process:
dwaadmindwastgstagingworking
If your organization uses Activate (formerly called KONNECT), it stores data in these schemas:
dealserviceeventservicefilemanagerkonnect
The pg_catalog and pg_internal schemas are part of Amazon Redshift.
The archive schema is rarely used and provides access to Amazon S3 for certain clients.
The public schema is rarely used and allows clients to make a subset of data available to vendors.