Invantive Composition for Word
Connector DataCache: Persistent data cache, data replication or data vault. |
Persistent data cache, data replication or data vault.
Code for use in settings.xml: DataCache
Alias: cache
Abbreviation: idc
Status: Production
Available in Editions: Paid
String-comparison is Case-sensitive: true
Use Catalog in Full Name: true
Use Schema in Full Name: true
Technical Documentation: https://documentation.invantive.com/2017R2/data-cache-data-model/webhelp/index.html
Provider Attributes
The following provider attributes are available for DataCache:
Code |
Description |
Default Value |
Set from Connection String |
Set from Set SQL-Statement |
Set from Providers File |
Set from Log On |
|---|---|---|---|---|---|---|
application-prefix-facts |
A prefix applied after the environment prefix to every facts table, index and view. |
dcd_ |
✓ |
|
|
|
application-prefix-history |
A prefix applied after the environment prefix to every history table, index and view. |
dcs_ |
✓ |
|
|
|
application-prefix-repository |
A prefix applied after the environment prefix to every repository table, index and view. |
dc_ |
✓ |
|
|
|
backing-bulk-insert-page-size-bytes |
Approximate maximum size in bytes of page when bulk inserting on backing database. |
|
✓ |
✓ |
✓ |
|
backing-bulk-insert-page-size-rows |
Number of rows to insert per page when bulk inserting on backing database. |
|
✓ |
✓ |
✓ |
|
backing-bulk-insert-timeout-sec |
Number of seconds after which a bulk insert on backing database times out. |
3600 |
✓ |
✓ |
✓ |
|
backing-command-timeout-sec |
Number of seconds after which a command on backing database times out. |
3600 |
✓ |
✓ |
✓ |
|
backing-connection-string |
The connection string for the backing database |
|
✓ |
|
✓ |
|
backing-force-case-sensitive-identifiers |
Consider identifiers on the backing database as case-sensitive independent of the platform capabilities. |
False |
✓ |
✓ |
✓ |
|
backing-forced-casing-identifiers |
Forced casing of identifiers on the backing database. Choose from Unset, Lower, Upper and Mixed. |
Unset |
✓ |
✓ |
✓ |
|
backing-maximum-length-identifiers |
Non-default maximum length on the backing database in characters of identifier names. |
|
✓ |
✓ |
✓ |
|
backing-maximum-number-of-pooled-connections |
Maximum number of concurrent pooled connections on backing database. |
|
✓ |
✓ |
✓ |
|
backing-maximum-sleep-acquire-pooled-connection-ms |
Maximum time in ms to wait for acquiring a free connection from a pool of connections on backing database. |
300000 |
✓ |
✓ |
✓ |
|
backing-maximum-sleep-acquire-unpooled-connection-ms |
Maximum time in ms to wait for acquire a free connection when there is no connection pooling on backing database. |
600000 |
✓ |
✓ |
✓ |
|
backing-minimum-connection-timeout-sec |
Minimum number of seconds after which a newly requested connection on backing database times out. |
300 |
✓ |
✓ |
✓ |
|
backing-preferred-number-of-pooled-connections |
Preferred number of concurrent pooled connections on backing database. |
|
✓ |
✓ |
✓ |
|
backing-provider |
Name of the Invantive connector for the backing database |
|
✓ |
|
✓ |
|
backing-sql-server-connect-retry-count |
Number of connect retries on connection failed on the backing SQL Server database (SQL Server only). |
60 |
✓ |
✓ |
✓ |
|
backing-sql-server-connect-retry-interval-sec |
Interval between connect retries on connection failed on the backing SQL Server database (SQL Server only).. |
15 |
✓ |
✓ |
✓ |
|
backing-standardize-identifiers |
Rewrite all identifiers on the backing database to the preferred standards as configured by standardize-identifiers-casing and maximum-length-identifiers. |
True |
✓ |
✓ |
✓ |
|
backing-standardize-identifiers-casing |
Rewrite all identifiers on the backing database to the platform-specific recommended standard casing when changing a data model on a case-dependent platform. |
True |
✓ |
✓ |
✓ |
|
beta-compress-facts-on-disk |
Whether to compress facts in the disk cache. |
True |
✓ |
✓ |
✓ |
|
beta-encrypt-facts-on-disk |
Whether to encrypt facts in the disk cache. |
True |
✓ |
✓ |
✓ |
|
beta-store-facts-in-database |
Whether to store facts in the database containing the repository. |
True |
✓ |
✓ |
✓ |
|
beta-store-facts-on-disk |
Whether to store facts in the disk cache. |
True |
✓ |
✓ |
✓ |
|
beta-use-facts-in-database |
Whether to use facts in the database cache. |
True |
✓ |
✓ |
✓ |
|
beta-use-facts-on-disk |
Whether to use facts in the disk cache. |
False |
✓ |
✓ |
✓ |
|
bulk-delete-page-size-rows |
Number of rows to delete per batch when bulk deleting |
10000 |
✓ |
✓ |
✓ |
|
bulk-insert-page-size-bytes |
Approximate maximum size in bytes of batch when bulk inserting |
10000000 |
✓ |
✓ |
✓ |
|
bulk-insert-page-size-rows |
Number of rows to insert per batch when bulk inserting |
10000 |
✓ |
✓ |
✓ |
|
cache-folder |
Folder to store Data Cache cache files in. |
C:\Users\gle3.WS212\Invantive\Cache\datacache |
✓ |
✓ |
✓ |
|
default-skip-client-side-cacheable |
Whether to skip client-side cacheable tables by default. |
True |
✓ |
✓ |
✓ |
|
default-use-ods |
Whether to use the Operational Data Store when no hint is specified. |
True |
✓ |
✓ |
✓ |
|
delete-number-table-partition-versions-per-group |
Maximum number of table partition versions selected in the IN-clause for a delete of facts. |
50 |
✓ |
✓ |
✓ |
|
development-use-http-disk-cache |
Whether to allow use of the disk cache for platform HTTP requests. |
False |
✓ |
✓ |
|
|
drop-backlog-factor |
Maximum ratio between number of versions dropped and new versions loaded on refresh. |
|
✓ |
✓ |
✓ |
|
environment-prefix-all |
A prefix applied to repository, facts and history database tables, indexes and views. |
|
✓ |
|
|
|
environment-prefix-facts |
A prefix applied to every facts table, index and view. |
|
✓ |
|
|
|
environment-prefix-history |
A prefix applied to every history table, index and view. |
|
✓ |
|
|
|
environment-prefix-logical-view |
A prefix applied to every logical view. |
|
✓ |
|
|
|
environment-prefix-repository |
A prefix applied to every repository table, index and view. |
|
✓ |
|
|
|
event-log-entries-delete-page-size-rows |
Number of rows to delete per batch on maintaining facts. |
1000 |
✓ |
✓ |
✓ |
|
event-log-memory-cache-flush-interval-sec |
Maximum intervla in seconds between flushes of in-memory cache of event log entries to database. |
15 |
✓ |
|
|
|
event-log-memory-cache-size |
Size of in-memory cache of event log entries before they are written to the database. |
100 |
✓ |
|
|
|
facts-delete-page-size-characters |
Number of characters to delete per batch on maintaining facts. |
10000000 |
✓ |
✓ |
✓ |
|
facts-delete-page-size-rows |
Number of rows to delete per batch on maintaining facts. |
|
✓ |
✓ |
✓ |
|
facts-insert-page-size-rows |
Number of rows to insert per batch on maintaining facts. |
|
✓ |
✓ |
✓ |
|
force-case-sensitive-identifiers |
Consider identifiers as case-sensitive independent of the platform capabilities. |
False |
✓ |
✓ |
✓ |
|
forced-casing-identifiers |
Forced casing of identifiers. Choose from Unset, Lower, Upper and Mixed. |
|
✓ |
✓ |
✓ |
|
forced-casing-logical-view-column-name |
Forced casing of logical view column names. Choose from Unset, Lower, Upper and Mixed. |
Unset |
✓ |
✓ |
✓ |
|
forced-casing-logical-view-name |
Forced casing of logical view names. Choose from Unset, Lower, Upper and Mixed. |
Unset |
✓ |
✓ |
✓ |
|
forwarded-incoming-messages-delete-max-runtime-sec |
Maximum runtime of purge forwarded incoming messages in seconds. |
3600 |
✓ |
✓ |
✓ |
|
forwarded-incoming-messages-delete-page-size-rows |
Number of rows to delete per batch on maintaining forwarded incoming messages. |
10000 |
✓ |
✓ |
✓ |
|
garbage-collection-physical-memory-load-threshold |
Percentage of physical memory load above which a full garbage collection is run after replication. |
80 |
✓ |
✓ |
✓ |
|
garbage-collection-replication-interval-count |
Number of replications after last garbage collection after which a full garbage collection is run. |
100 |
✓ |
✓ |
✓ |
|
garbage-collection-replication-minimum-interval-sec |
Minimum interval in seconds between two full garbage collections.. |
30 |
✓ |
✓ |
✓ |
|
invantive-sql-forward-filters-to-data-containers |
Whether to forward filters to data containers. |
True |
✓ |
✓ |
✓ |
|
invantive-sql-shuffle-fetch-results-data-containers |
Whether to shuffle results fetched from data containers. |
False |
✓ |
✓ |
✓ |
|
invantive-use-cache |
Whether to cache the results of a query. |
True |
✓ |
✓ |
✓ |
|
log-native-calls-to-disk |
Registers native calls to data container backend as disk files. |
False |
✓ |
✓ |
✓ |
|
log-native-calls-to-trace |
Log native calls to data container backend on the trace. |
False |
✓ |
✓ |
✓ |
|
max-delete-facts-parallel |
Maximum number of parallel deletes on facts tables. |
8 |
✓ |
✓ |
✓ |
|
maximum-length-identifiers |
Non-default maximum length in characters of identifier names. |
|
✓ |
✓ |
✓ |
|
maximum-length-logical-view-column-name |
Maximum length of logical view column names. |
|
✓ |
✓ |
✓ |
|
maximum-length-logical-view-name |
Maximum length of logical view names. |
|
✓ |
✓ |
✓ |
|
max-messages-per-customer-service-request |
Maximum number of messages to download from Customer Service per request. |
10000 |
✓ |
✓ |
✓ |
|
max-refreshes-parallel |
Maximum number of parallel refreshes. |
32 |
✓ |
✓ |
✓ |
|
max-url-length-accepted |
The maximum accepted URL length before raising an error. |
8000 |
✓ |
✓ |
✓ |
|
max-url-length-desired |
The maximum desired URL length. |
8000 |
✓ |
✓ |
✓ |
|
orphaned-facts-delete-page-size-rows |
Number of rows to delete per batch on purging orphaned facts during repository upgrade or maintenance. |
10000 |
✓ |
✓ |
✓ |
|
partition-slot-based-rate-limit-length-ms |
Total length in ms across all slots of a partition-based rate limit. |
60000 |
✓ |
|
✓ |
|
partition-slot-based-rate-limit-slots |
Number of slots per partition-based rate limit. Null means no slot-based rate limit |
|
✓ |
|
✓ |
|
pre-request-delay-ms |
Pre-request delay in milliseconds per request. |
0 |
✓ |
✓ |
✓ |
|
purge-interval-event-log-entries-minutes |
Interval in minutes between completed purges of ancient event log entries. |
60 |
✓ |
✓ |
✓ |
|
requested-page-size |
Preferred number of rows to exchange per round trip; only effective on limited platforms such as AFAS Online |
|
✓ |
✓ |
✓ |
|
requests-parallel-max |
Maximum number of parallel data requests from individual partitions on the data container. |
32 |
✓ |
✓ |
✓ |
|
retention-event-log-entries-days |
Retention of event log entries in days. |
35 |
✓ |
✓ |
✓ |
|
slot-based-rate-limit-length-ms |
Total length in ms across all slots of a slot-based rate limit. |
60000 |
✓ |
|
✓ |
|
slot-based-rate-limit-slots |
Number of slots of a slot-based rate limit. Null means no slot-based rate limit |
|
✓ |
|
✓ |
|
standardize-identifiers |
Rewrite all identifiers to the preferred standards as configured by standardize-identifiers-casing and maximum-length-identifiers. |
True |
✓ |
✓ |
✓ |
|
standardize-identifiers-casing |
Rewrite all identifiers to the recommended standard platform-specific casing when changing a data model on a case-dependent platform. |
True |
✓ |
✓ |
✓ |
|
update-number-table-partition-versions-per-group |
Maximum number of table partition versions selected in the IN-clause for an update of metadata. |
1000 |
✓ |
✓ |
✓ |
|
upgrade-force-execute |
Whether to force execution of possible upgrade steps, even when there are no reasons to perform an upgrade. |
False |
✓ |
|
|
|
upgrade-force-repository-version-start |
Specifies the repository version to start upgrade from when specified. |
|
✓ |
|
|
|
upgrade-force-specials |
Execute special operations before the repository is opened. |
|
✓ |
|
|
|
26-06-2020 06:4820.1.99-BETA+2846
