Data Cache Data ModelThe SQL driver for Data Cache has many attributes that can be finetuned to improve handling in scenarios with unreliable network connections to the Data Cache server or high-volumes of data. Also, many drivers have driver-specific attributes to finetune actual behaviour or handle data not matching specifications.
The Data Cache driver attributes are assigned a default value which seldom requires change. However, changes can be applied when needed on four levels, which are reflected in the table below by separate checkmarks:
•Connection string: the connection string from the settings*.xml file and applied during log on.
•Set SQL statement: a set SQL-statement to be executed once connection has been established.
•Drivers file: the providers.xml file (obsolete starting release 17.32).
•Log on: value to be specified interactively by user during log on in a user interface.
The connection string for Data Cache can be found in the settings*.xml file used for the database. Settings*.xml files are typically located in the %USERPROFILE%\invantive folder in most deployment scenarios. The reference manuals contain instructions how to relocate the settings*.xml files. Each data container of a database in the connection string can have a connectionString element specifying the name and values of attributes. Both name and value must be properly escaped according to XML-semantics. Actual application of the value is solely done during log on. A new connection must be established to change the value of a driver attribute using a connection string.
The set SQL statement can be executed after log on. The syntax is: set NAME VALUE, or for a distributed database: set NAME@ALIAS VALUE. In some scenarios you may need to enclose the driver attribute name in square brackets to escape it from parsing, for instance when a reserved SQL keyword is part of the name. The new value takes effect straight after execution of the set-statement. The set-statement can be executed as often as needed during a session.
Driver attributes that can be interactively set to a value are typically presented in the log on window. Depending on the platform and design decisions of the user interface designer, some or all of the available driver attributes can have been made available.
The Data Cache driver can be configured using the following attributes:
Code |
Description |
Origin |
Default Value |
Set from Connection String |
Set from Set SQL-Statement |
Set from Drivers File |
Set from Log On |
|---|---|---|---|---|---|---|---|
analysis-enforce-row-uniqueness |
Use for analysis only! Enforce rows to be unique. |
Shared |
False |
✓ |
✓ |
✓ |
|
application-prefix-facts |
A prefix applied after the environment prefix to every facts table, index and view. |
Data Cache |
dcd_ |
✓ |
|
|
|
application-prefix-history |
A prefix applied after the environment prefix to every history table, index and view. |
Data Cache |
dcs_ |
✓ |
|
|
|
application-prefix-repository |
A prefix applied after the environment prefix to every repository table, index and view. |
Data Cache |
dc_ |
✓ |
|
|
|
backing-bulk-insert-page-size-bytes |
Approximate maximum size in bytes of page when bulk inserting on backing database. |
Data Cache |
|
✓ |
✓ |
✓ |
|
backing-bulk-insert-page-size-rows |
Number of rows to insert per page when bulk inserting on backing database. |
Data Cache |
|
✓ |
✓ |
✓ |
|
backing-bulk-insert-timeout-sec |
Number of seconds after which a bulk insert on backing database times out. |
Data Cache |
3600 |
✓ |
✓ |
✓ |
|
backing-command-timeout-sec |
Number of seconds after which a command on backing database times out. |
Data Cache |
3600 |
✓ |
✓ |
✓ |
|
backing-connection-string |
The connection string for the backing database |
Data Cache |
|
✓ |
|
✓ |
|
backing-force-case-sensitive-identifiers |
Consider identifiers on the backing database as case-sensitive independent of the platform capabilities. |
Data Cache |
False |
✓ |
✓ |
✓ |
|
backing-forced-casing-identifiers |
Forced casing of identifiers on the backing database. Choose from Unset, Lower, Upper and Mixed. |
Data Cache |
Unset |
✓ |
✓ |
✓ |
|
backing-maximum-length-identifiers |
Non-default maximum length on the backing database in characters of identifier names. |
Data Cache |
|
✓ |
✓ |
✓ |
|
backing-maximum-number-of-pooled-connections |
Maximum number of concurrent pooled connections on backing database. |
Data Cache |
|
✓ |
✓ |
✓ |
|
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. |
Data Cache |
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. |
Data Cache |
600000 |
✓ |
✓ |
✓ |
|
backing-minimum-connection-timeout-sec |
Minimum number of seconds after which a newly requested connection on backing database times out. |
Data Cache |
300 |
✓ |
✓ |
✓ |
|
backing-preferred-number-of-pooled-connections |
Preferred number of concurrent pooled connections on backing database. |
Data Cache |
|
✓ |
✓ |
✓ |
|
backing-provider |
Name of the Invantive connector for the backing database |
Data Cache |
|
✓ |
|
✓ |
|
backing-sql-server-connect-retry-count |
Number of connect retries on connection failed on the backing SQL Server database (SQL Server only). |
Data Cache |
60 |
✓ |
✓ |
✓ |
|
backing-sql-server-connect-retry-interval-sec |
Interval between connect retries on connection failed on the backing SQL Server database (SQL Server only).. |
Data Cache |
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. |
Data Cache |
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. |
Data Cache |
True |
✓ |
✓ |
✓ |
|
beta-compress-facts-on-disk |
Whether to compress facts in the disk cache. |
Data Cache |
True |
✓ |
✓ |
✓ |
|
beta-encrypt-facts-on-disk |
Whether to encrypt facts in the disk cache. |
Data Cache |
True |
✓ |
✓ |
✓ |
|
beta-store-facts-in-database |
Whether to store facts in the database containing the repository. |
Data Cache |
True |
✓ |
✓ |
✓ |
|
beta-store-facts-on-disk |
Whether to store facts in the disk cache. |
Data Cache |
True |
✓ |
✓ |
✓ |
|
beta-use-facts-in-database |
Whether to use facts in the database cache. |
Data Cache |
True |
✓ |
✓ |
✓ |
|
beta-use-facts-on-disk |
Whether to use facts in the disk cache. |
Data Cache |
False |
✓ |
✓ |
✓ |
|
bulk-delete-page-size-rows |
Number of rows to delete per batch when bulk deleting |
Shared |
10000 |
✓ |
✓ |
✓ |
|
bulk-insert-page-size-bytes |
Approximate maximum size in bytes of batch when bulk inserting |
Shared |
10000000 |
✓ |
✓ |
✓ |
|
bulk-insert-page-size-rows |
Number of rows to insert per batch when bulk inserting |
Shared |
10000 |
✓ |
✓ |
✓ |
|
cache-folder |
Folder to store Data Cache cache files in. |
Data Cache |
C:\Users\gle3.WS212\Invantive\Cache\datacache |
✓ |
✓ |
✓ |
|
default-skip-client-side-cacheable |
Whether to skip client-side cacheable tables by default. |
Data Cache |
True |
✓ |
✓ |
✓ |
|
default-use-ods |
Whether to use the Operational Data Store when no hint is specified. |
Data Cache |
True |
✓ |
✓ |
✓ |
|
delete-number-table-partition-versions-per-group |
Maximum number of table partition versions selected in the IN-clause for a delete of facts. |
Data Cache |
50 |
✓ |
✓ |
✓ |
|
development-use-http-disk-cache |
Whether to allow use of the disk cache for platform HTTP requests. |
Data Cache |
False |
✓ |
✓ |
|
|
drop-backlog-factor |
Maximum ratio between number of versions dropped and new versions loaded on refresh. |
Data Cache |
|
✓ |
✓ |
✓ |
|
environment-prefix-all |
A prefix applied to repository, facts and history database tables, indexes and views. |
Data Cache |
|
✓ |
|
|
|
environment-prefix-facts |
A prefix applied to every facts table, index and view. |
Data Cache |
|
✓ |
|
|
|
environment-prefix-history |
A prefix applied to every history table, index and view. |
Data Cache |
|
✓ |
|
|
|
environment-prefix-logical-view |
A prefix applied to every logical view. |
Data Cache |
|
✓ |
|
|
|
environment-prefix-repository |
A prefix applied to every repository table, index and view. |
Data Cache |
|
✓ |
|
|
|
event-log-entries-delete-page-size-rows |
Number of rows to delete per batch on maintaining facts. |
Data Cache |
1000 |
✓ |
✓ |
✓ |
|
event-log-memory-cache-flush-interval-sec |
Maximum intervla in seconds between flushes of in-memory cache of event log entries to database. |
Data Cache |
15 |
✓ |
|
|
|
event-log-memory-cache-size |
Size of in-memory cache of event log entries before they are written to the database. |
Data Cache |
100 |
✓ |
|
|
|
facts-delete-page-size-characters |
Number of characters to delete per batch on maintaining facts. |
Data Cache |
10000000 |
✓ |
✓ |
✓ |
|
facts-delete-page-size-rows |
Number of rows to delete per batch on maintaining facts. |
Data Cache |
|
✓ |
✓ |
✓ |
|
facts-insert-page-size-rows |
Number of rows to insert per batch on maintaining facts. |
Data Cache |
|
✓ |
✓ |
✓ |
|
force-case-sensitive-identifiers |
Consider identifiers as case-sensitive independent of the platform capabilities. |
Shared |
False |
✓ |
✓ |
✓ |
|
forced-casing-identifiers |
Forced casing of identifiers. Choose from Unset, Lower, Upper and Mixed. |
Shared |
|
✓ |
✓ |
✓ |
|
forced-casing-logical-view-column-name |
Forced casing of logical view column names. Choose from Unset, Lower, Upper and Mixed. |
Data Cache |
Unset |
✓ |
✓ |
✓ |
|
forced-casing-logical-view-name |
Forced casing of logical view names. Choose from Unset, Lower, Upper and Mixed. |
Data Cache |
Unset |
✓ |
✓ |
✓ |
|
forwarded-incoming-messages-delete-max-runtime-sec |
Maximum runtime of purge forwarded incoming messages in seconds. |
Data Cache |
3600 |
✓ |
✓ |
✓ |
|
forwarded-incoming-messages-delete-page-size-rows |
Number of rows to delete per batch on maintaining forwarded incoming messages. |
Data Cache |
10000 |
✓ |
✓ |
✓ |
|
garbage-collection-physical-memory-load-threshold |
Percentage of physical memory load above which a full garbage collection is run after replication. |
Data Cache |
80 |
✓ |
✓ |
✓ |
|
garbage-collection-replication-interval-count |
Number of replications after last garbage collection after which a full garbage collection is run. |
Data Cache |
100 |
✓ |
✓ |
✓ |
|
garbage-collection-replication-minimum-interval-sec |
Minimum interval in seconds between two full garbage collections.. |
Data Cache |
30 |
✓ |
✓ |
✓ |
|
invantive-sql-correct-invalid-date |
Whether to correct dates considered invalid since they are before 01-01-1753. When nullable, they are removed. Otherwise they are replaced by 01-01-1753. |
SQL Engine V1 |
False |
✓ |
✓ |
✓ |
|
invantive-sql-forward-filters-to-data-containers |
Whether to forward filters to data containers. |
SQL Engine V1 |
True |
✓ |
✓ |
✓ |
|
invantive-sql-shuffle-fetch-results-data-containers |
Whether to shuffle results fetched from data containers. |
SQL Engine V1 |
False |
✓ |
✓ |
✓ |
|
invantive-use-cache |
Whether to cache the results of a query. |
SQL Engine V1 |
True |
✓ |
✓ |
✓ |
|
log-native-calls-to-disk |
Registers native calls to data container backend as disk files. |
Shared |
False |
✓ |
✓ |
✓ |
|
log-native-calls-to-trace |
Log native calls to data container backend on the trace. |
Shared |
False |
✓ |
✓ |
✓ |
|
max-delete-facts-parallel |
Maximum number of parallel deletes on facts tables. |
Data Cache |
8 |
✓ |
✓ |
✓ |
|
maximum-length-identifiers |
Non-default maximum length in characters of identifier names. |
Shared |
|
✓ |
✓ |
✓ |
|
maximum-length-logical-view-column-name |
Maximum length of logical view column names. |
Data Cache |
|
✓ |
✓ |
✓ |
|
maximum-length-logical-view-name |
Maximum length of logical view names. |
Data Cache |
|
✓ |
✓ |
✓ |
|
max-messages-per-customer-service-request |
Maximum number of messages to download from Customer Service per request. |
Data Cache |
10000 |
✓ |
✓ |
✓ |
|
max-refreshes-parallel |
Maximum number of parallel refreshes. |
Data Cache |
32 |
✓ |
✓ |
✓ |
|
max-url-length-accepted |
The maximum accepted URL length before raising an error. |
Shared |
8000 |
✓ |
✓ |
✓ |
|
max-url-length-desired |
The maximum desired URL length. |
Shared |
8000 |
✓ |
✓ |
✓ |
|
orphaned-facts-delete-page-size-rows |
Number of rows to delete per batch on purging orphaned facts during repository upgrade or maintenance. |
Data Cache |
10000 |
✓ |
✓ |
✓ |
|
partition-slot-based-rate-limit-length-ms |
Total length in ms across all slots of a partition-based rate limit. |
Shared |
60000 |
✓ |
|
✓ |
|
partition-slot-based-rate-limit-slots |
Number of slots per partition-based rate limit. Null means no slot-based rate limit |
Shared |
|
✓ |
|
✓ |
|
pre-request-delay-ms |
Pre-request delay in milliseconds per request. |
Shared |
0 |
✓ |
✓ |
✓ |
|
purge-interval-event-log-entries-minutes |
Interval in minutes between completed purges of ancient event log entries. |
Data Cache |
60 |
✓ |
✓ |
✓ |
|
requested-page-size |
Preferred number of rows to exchange per round trip; only effective on limited platforms such as AFAS Online |
Shared |
|
✓ |
✓ |
✓ |
|
requests-parallel-max |
Maximum number of parallel data requests from individual partitions on the data container. |
Shared |
32 |
✓ |
✓ |
✓ |
|
retention-event-log-entries-days |
Retention of event log entries in days. |
Data Cache |
35 |
✓ |
✓ |
✓ |
|
slot-based-rate-limit-length-ms |
Total length in ms across all slots of a slot-based rate limit. |
Shared |
60000 |
✓ |
|
✓ |
|
slot-based-rate-limit-slots |
Number of slots of a slot-based rate limit. Null means no slot-based rate limit |
Shared |
|
✓ |
|
✓ |
|
standardize-identifiers |
Rewrite all identifiers to the preferred standards as configured by standardize-identifiers-casing and maximum-length-identifiers. |
Shared |
True |
✓ |
✓ |
✓ |
|
standardize-identifiers-casing |
Rewrite all identifiers to the recommended standard platform-specific casing when changing a data model on a case-dependent platform. |
Shared |
True |
✓ |
✓ |
✓ |
|
update-number-table-partition-versions-per-group |
Maximum number of table partition versions selected in the IN-clause for an update of metadata. |
Data Cache |
1000 |
✓ |
✓ |
✓ |
|
upgrade-force-execute |
Whether to force execution of possible upgrade steps, even when there are no reasons to perform an upgrade. |
Data Cache |
False |
✓ |
|
|
|
upgrade-force-repository-version-start |
Specifies the repository version to start upgrade from when specified. |
Data Cache |
|
✓ |
|
|
|
upgrade-force-specials |
Execute special operations before the repository is opened. |
Data Cache |
|
✓ |
|
|
|
09-12-2020 18:57 Version 20.1.300-BETA+3020
