Jump to: navigation, search

partitioning-interval-size-gim

Section: gim-etl
Default Value: 86400
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None

Specifies the size of partitions, in seconds, for Info Mart fact and Control tables that are partitioned. Job_MaintainGIM creates partitions of the specified size in the Info Mart database in preparation for future ETL cycles. Starting with release 8.1.1, the default size of Info Mart fact table partitions is 1 day (86400 seconds). In release 8.1.0, the default size was 7 days (604800 seconds).

more...

partitioning-interval-size-gidb-ocs

Section: gim-etl
Default Value: 86400 or partitioning-interval-size-gidb
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Introduced: 8.1.402.07

Specifies the size of partitions, in seconds, for partitioned GIDB tables that store Outbound Contact–related data. When this option is set, Job_MaintainGIM creates partitions of the specified size in the Info Mart database in preparation for future ETL cycles. If the option is not specified, the value of partitioning-interval-size-gidb, which has a default value of 24 hours (86400 seconds), is used.

more...

partitioning-interval-size-gidb-mm

Section: gim-etl
Default Value: 86400 or partitioning-interval-size-gidb
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Introduced: 8.1.402.07

Specifies the size of partitions, in seconds, for partitioned GIDB tables that store multimedia interaction data. When this option is set, Job_MaintainGIM creates partitions of the specified size in the Info Mart database in preparation for future ETL cycles. If the option is not specified, the value of partitioning-interval-size-gidb, which has a default value of 24 hours (86400 seconds), is used. Genesys recommends increasing the size of GIDB partitions for multimedia interactions, which typically live longer than voice interactions but generate a smaller volume of data.

more...

partitioning-interval-size-gidb

Section: gim-etl
Default Value: 86400
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None

Specifies the size of partitions, in seconds, for GIDB tables that are partitioned. Job_MaintainGIM creates partitions of the specified size in the Info Mart database in preparation for future ETL cycles. The default size of GIDB table partitions is 24 hours (86400 seconds).

more...

partitioning-interval-size-gim

Section: gim-etl
Default Value: 86400
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None

Specifies the size of partitions, in seconds, for Info Mart fact and Control tables that are partitioned. Job_MaintainGIM creates partitions of the specified size in the Info Mart database in preparation for future ETL cycles. Starting with release 8.1.1, the default size of Info Mart fact table partitions is 1 day (86400 seconds). In release 8.1.0, the default size was 7 days (604800 seconds).

more...

Info Mart Partitioning

For general information about partitioning in the Info Mart database, see Database Partitioning in the Deployment Guide.

This page provides a comprehensive list of tables for which partitions are created in a partitioned Info Mart database, grouped as follows:

The name of the key by which a table is partitioned is included for each table.

Partitioned Dimensional Model Fact Tables

Dimensional Model fact tables are partitioned by the Start Date Time key. The size of the partitions is determined by the partitioning-interval-size-gim configuration option.


Table Partitioned by Key
BGS_SESSION_FACT START_DATE_TIME_KEY
CALLBACK_FACT START_DATE_TIME_KEY
CALLING_LIST_METRIC_FACT START_DATE_TIME_KEY
CAMPAIGN_GROUP_SESSION_FACT START_DATE_TIME_KEY
CAMPAIGN_GROUP_STATE_FACT START_DATE_TIME_KEY
CHAT_SESSION_FACT START_DATE_TIME_KEY
CONTACT_ATTEMPT_FACT START_DATE_TIME_KEY
GPM_FACT START_DATE_TIME_KEY
INTERACTION_FACT START_DATE_TIME_KEY
INTERACTION_RESOURCE_FACT START_DATE_TIME_KEY
IRF_USER_DATA_CUST_1 START_DATE_TIME_KEY
IRF_USER_DATA_GEN_1 START_DATE_TIME_KEY
IRF_USER_DATA_KEYS START_DATE_TIME_KEY
IXN_RESOURCE_STATE_FACT START_DATE_TIME_KEY
MEDIATION_SEGMENT_FACT START_DATE_TIME_KEY
SDR_ACTIVITIES_FACT START_DATE_TIME_KEY
SDR_CUST_ATRIBUTES_FACT START_DATE_TIME_KEY
SDR_EXT_REQUEST_FACT START_DATE_TIME_KEY
SDR_SESSION_FACT START_DATE_TIME_KEY
SDR_SURVEY_FACT START_DATE_TIME_KEY
SDR_SURVEY_TRANSCRIPT_FACT START_DATE_TIME_KEY
SDR_USER_INPUTS_FACT START_DATE_TIME_KEY
SDR_USER_MILESTONE_FACT START_DATE_TIME_KEY
SM_MEDIA_NEUTRAL_STATE_FACT START_DATE_TIME_KEY
SM_RES_SESSION_FACT START_DATE_TIME_KEY
SM_RES_STATE_FACT START_DATE_TIME_KEY
SM_RES_STATE_REASON_FACT START_DATE_TIME_KEY
STG_TRANSFORM_DISCARDS START_DATE_TIME_KEY

Partitioned GIDB Fact Tables

Keys used for partitioning of GIDB fact tables vary from table to table. The size of the partitions is determined by the partitioning-interval-size-gidb configuration option, which you can override for Multimedia- and Outbound Contact–related data by specifying different values for the partitioning-interval-size-gidb-mm and partitioning-interval-size-gidb-ocs configuration options, respectively. In the following table:

  • No asterisk means that partition size is always controlled by the partitioning-interval-size-gidb option (default is 24 hours).
  • A single asterisk (*) indicates that partition size can be controlled by the partitioning-interval-size-gidb-mm option.
  • A double asterisk (**) indicates that partition size can be controlled by the partitioning-interval-size-gidb-ocs option.
Table Partitioned by Key
GIDB_G_AGENT_STATE_HISTORY_MM* ADDED_TS
GIDB_G_AGENT_STATE_HISTORY_V ADDED_TS
GIDB_G_AGENT_STATE_RC_MM* CREATED_TS
GIDB_G_AGENT_STATE_RC_V CREATED_TS
GIDB_G_CALL_HISTORY_MM* ADDED_TS
GIDB_G_CALL_HISTORY_V ADDED_TS
GIDB_G_CALL_MM* CREATED_TS
GIDB_G_CALL_STAT_V GSYS_EXT_INT2
GIDB_G_CALL_V CREATED_TS
GIDB_G_CUSTOM_DATA_S_MM* ADDED_TS
GIDB_G_CUSTOM_DATA_S_V ADDED_TS
GIDB_G_DND_HISTORY_MM* ADDED_TS
GIDB_G_DND_HISTORY_V ADDED_TS
GIDB_G_IR_HISTORY_MM* ADDED_TS
GIDB_G_IR_HISTORY_V ADDED_TS
GIDB_G_IR_MM* CREATED_TS
GIDB_G_IR_V CREATED_TS
GIDB_G_IS_LINK_HISTORY_V ADDED_TS
GIDB_G_IS_LINK_V INITIATED_TS
GIDB_G_LOGIN_SESSION_MM* CREATED_TS
GIDB_G_LOGIN_SESSION_V CREATED_TS
GIDB_G_PARTY_HISTORY_MM* ADDED_TS
GIDB_G_PARTY_HISTORY_V ADDED_TS
GIDB_G_PARTY_MM* CREATED_TS
GIDB_G_PARTY_V CREATED_TS
GIDB_G_ROUTE_RESULT_MM* CREATED_TS
GIDB_G_ROUTE_RESULT_V CREATED_TS
GIDB_G_SECURE_UD_HISTORY_MM* ADDED_TS
GIDB_G_SECURE_UD_HISTORY_V ADDED_TS
GIDB_G_USERDATA_HISTORY_MM* ADDED_TS
GIDB_G_USERDATA_HISTORY_V ADDED_TS
GIDB_G_VIRTUAL_QUEUE_MM* CREATED_TS
GIDB_G_VIRTUAL_QUEUE_V CREATED_TS
GIDB_GM_F_USERDATA* GSYS_EXT_INT1
GIDB_GM_L_USERDATA* GSYS_EXT_INT2
GIDB_GO_CAMPAIGN** CREATED_TS
GIDB_GO_CAMPAIGNHISTORY** ADDED_TS
GIDB_GO_CHAIN** CREATED_TS
GIDB_GO_CHAINREC_HIST** ADDED_TS
GIDB_GO_FIELDHIST** ADDED_TS
GIDB_GO_METRICS** ADDED_TS
GIDB_GO_SEC_FIELDHIST** ADDED_TS
GIDB_GOX_CHAIN_CALL** ADDED_TS
GIDB_GX_SESSION_ENDPOINT_MM* CREATED_TS
GIDB_GX_SESSION_ENDPOINT_V CREATED_TS

Partitioned Control Tables

Control tables are partitioned by the created timestamp. The size of the partitions is determined by the partitioning-interval-size-gim configuration option.

Table Partitioned by Key
CTL_AUDIT_LOG CREATED_TS
CTL_ETL_HISTORY CREATED_TS
CTL_EXTRACT_HISTORY CREATED_TS
CTL_PURGE_HISTORY CREATED_TS
CTL_TRANSFORM_HISTORY CREATED_TS

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 18 August 2016, at 14:51.