If your organization uses any KORE CRM products, you can access much of the raw data through DWA. This data is stored in the
korepss schema. (PSS, or Pro Sports Standard, is a legacy name for KORE's CRM products.)
korepss schema contains a large number of tables. Many of these will contain no data, such as the
_staging tables used during import. Some tables are only used by a small number of KORE clients, and others may be deprecated.
Several tables are shared between more than one CRM product, such as the
kore_seasonbase table. These tables are illustrated below.
For product-specific information, see the integration catalog pages:
Most tables in the
korepss schema follow these conventions:
- Prefixed with
kore_to indicate the data comes from KORE's SQL Server
- Ends with
baseif the table contains standard fields
- Ends with
extensionif the table contains custom fields
- Postfixed with
_stagingif the table is only used during data sync
Some tables are used to store frequently-combined data for faster access (instead of using
JOIN every time). These tables follow the pattern
KORE Ticketing users will also have data in some of these tables, depending on which vendor(s) are used:
PV stands for ProVenue, the platform used by Tickets.com.
ERD for shared tables
Note: For clarity, many column names are omitted from this diagram.
Tip: Click the diagram to enlarge it. You can then click the pencil icon in the bottom toolbar to open a copy of it on diagrams.net. There, you can click an arrow to make its path more visible, move boxes around as you please, and more.
Column names beginning with
sf_ refer to information in your CRM, regardless of whether you use Salesforce or Dynamics 365. For example,
kore_contractbase.sf_dealsheetid specifies a deal sheet number within your CRM.