Navigation: Invantive SQL > Providers

Connector Data Dictionary: Invantive UniversalSQL data dictionary.

Invantive UniversalSQL data dictionary.

Code for use in settings.xml: DataDictionary

Alias: dd

Abbreviation: dd

Status: Production

Available in Editions: Paid

String-comparison is Case-sensitive: true

Use Catalog in Full Name: true

Use Schema in Full Name: true

Connector Attributes

The Data Dictionary connector can be configured using the following attributes:

Code	Description	Default Value	Set from Connection String	Set from Set SQL-Statement	Set from Connectors File
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	✓	✓	✓
connection-string	The connection string for the backing database		✓		✓
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.		✓	✓	✓
http-disk-cache-compression-level	Compression level for the HTTP disk cache, ranging from 1 (little) to 9 (intense). Default is 5.	5	✓	✓	✓
http-disk-cache-directory	Directory where HTTP cache is stored.	C:\Users\gle3.WS212\Invantive\Cache\http\gle3\shared	✓	✓	✓
http-disk-cache-ignore-write-errors	Whether to ignore write errors to disk cache.	False	✓	✓	✓
http-disk-cache-max-age-sec	Maximum acceptable age in seconds for use of data in the HTTP disk cache.	2592000	✓	✓	✓
invantive-sql-correct-invalid-date	Whether to correct invalid dates.	False	✓	✓	✓
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	✓	✓	✓
maximum-length-identifiers	Non-default maximum length in characters of identifier names.		✓	✓	✓
max-url-length-accepted	The maximum accepted URL length before raising an error.	8000	✓	✓	✓
max-url-length-desired	The maximum desired URL length.	8000	✓	✓	✓
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	✓	✓	✓
provider	Name of the Invantive connector for the backing database		✓		✓
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	✓	✓	✓
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	✓	✓	✓
use-http-disk-cache-read	Whether to use HTTP responses from previous queries stored on disk to answer the current query.	False	✓	✓	✓
use-http-disk-cache-write	Whether to memorize HTTP responses on disk.	False	✓	✓	✓

10-09-2020 00:0720.1.206-BETA+2915

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Invantive Web Service Estate Forums

Connector Data Dictionary: Invantive UniversalSQL data dictionary.

Connector Attributes

Important Safety and Usage Information