Navigatie: » Geen onderwerpen boven dit niveau «

Company.info SQL Driver Attributes

The SQL driver for Company.info has many attributes that can be finetuned to improve handling in scenarios with unreliable network connections to the API server of Company.info or high-volumes of data. Also, many drivers have driver-specific attributes to finetune actual behaviour or handle data not matching specifications.

The Company.info 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 Company.info 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 Company.info 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	✓	✓	✓
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	✓	✓	✓
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		✓	✓	✓
http-disk-cache-compression-level	Compression level for the HTTP disk cache, ranging from 1 (little) to 9 (intense). Default is 5.	Shared	5	✓	✓	✓
http-disk-cache-directory	Directory where HTTP cache is stored.	Shared	C:\Users\gle3.WS212\Invantive\Cache\http\gle3\shared	✓	✓	✓
http-disk-cache-ignore-write-errors	Whether to ignore write errors to disk cache.	Shared	False	✓	✓	✓
http-disk-cache-max-age-sec	Maximum acceptable age in seconds for use of data in the HTTP disk cache.	Shared	2147483647	✓	✓	✓
http-get-timeout-max-ms	HTTP GET timeout maximum on retry (ms)		300000	✓	✓	✓
http-get-timeout-ms	HTTP GET timeout (ms)		60000	✓	✓	✓
http-memory-cache-compression-level	Compression level for the HTTP memory cache, ranging from 1 (little) to 9 (intense). Default is 5.		5	✓	✓	✓
http-memory-cache-max-age-sec	Maximum acceptableage in seconds for use of data in the HTTP memory cache.		2147483647	✓	✓	✓
http-post-timeout-max-ms	HTTP POST timeout maximum on retry (ms)		300000	✓	✓	✓
http-post-timeout-ms	HTTP POST timeout (ms)		300000	✓	✓	✓
invantive-sql-compress-sparse-arrays	Whether to compress sparse arrays in result sets during compression.	SQL Engine V1	True	✓	✓	✓
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-share-byte-arrays	Whether to share the memory used by identical byte arrays in result sets during compression.	SQL Engine V1	True	✓	✓	✓
invantive-sql-share-strings	Whether to share the memory used by identical strings in result sets during compression.	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-max-events	Maximum number of events to register from last activation.	Shared		✓	✓	✓
log-native-calls-to-disk-max-seconds	Maximum number of seconds to register from last activation.	Shared		✓	✓	✓
log-native-calls-to-disk-on-error	Registers native calls to data container backend as disk files when an error occurred.	Shared	False	✓	✓	✓
log-native-calls-to-disk-on-success	Registers native calls to data container backend as disk files when successful.	Shared	False	✓	✓	✓
log-native-calls-to-trace	Log native calls to data container backend on the trace.	Shared	False	✓	✓	✓
maximum-length-identifiers	Non-default maximum length in characters of identifier names.	Shared		✓	✓	✓
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	✓	✓	✓
minimum-length-text	Extend all text columns to this length to allow processing of XML that uses longer text values than the XSD specifies.	XML		✓			✓
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	✓	✓	✓
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	✓	✓	✓
result-set-memory-cache	Action: provide 'empty' to empty.	XML			✓
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	✓	✓	✓
use-fallback-environment	Use fallback environment.	Company.info		✓		✓
use-http-disk-cache-read	Whether to use HTTP responses from previous queries stored on disk to answer the current query.	Shared	True	✓	✓	✓
use-http-disk-cache-write	Whether to memorize HTTP responses on disk.	Shared	True	✓	✓	✓
use-http-memory-cache-read	Whether to use HTTP responses from previous queries stored in memory to answer the current query		True	✓	✓	✓
use-http-memory-cache-write	Whether to memorize HTTP responses in memory		True	✓	✓	✓
use-metadata-memory-cache	Whether to use the metadata in memory calculated previously Has only practical use during development on a XML provider.	XML	True	✓	✓	✓
use-result-memory-cache	Whether to use result sets cached in memory from previous queries that can answer the current query.	XML	False	✓	✓	✓

15-06-2022 23:19 Version 22.1.46-BETA+3385

Belangrijke Informatie over Veiligheid en Gebruik

Beoogd gebruik en beperkingen: Deze software, ontwikkeld door Invantive, is ontworpen om een verscheidenheid aan zakelijke en informatietechnologische gegevensverwerkingsfuncties te ondersteunen, zoals boekhouding, financiÃ«le rapportage en verkooprapportage. Het is belangrijk om op te merken dat deze software niet is ontworpen, getest of goedgekeurd voor gebruik in omgevingen waar een storing of defect kan leiden tot levensbedreigende situaties, ernstige fysieke schade of milieuschade. Dit omvat, maar is niet beperkt tot:

Nucleaire faciliteiten: de software mag niet worden gebruikt voor operaties of functies die verband houden met de controle, het onderhoud of de werking van nucleaire faciliteiten.
Defensie en militaire toepassingen: deze software is niet geschikt voor gebruik in defensiegerelateerde toepassingen, inclusief maar niet beperkt tot wapenbeheer, militaire strategieplanning of andere aspecten van nationale defensie.
Luchtvaart: de software is niet bedoeld voor gebruik in de bediening, navigatie of communicatiesystemen van vliegtuigen of luchtverkeersleidingomgevingen.
Gezondheidszorg en medicijnproductie: deze software mag niet worden gebruikt voor de werking van medische apparaten, de analyse van patiÃ«ntgegevens voor kritieke gezondheidsbeslissingen, farmaceutische productie of medisch onderzoek waarbij een storing of defect de gezondheid van de patiÃ«nt kan beÃ¯nvloeden.
Verwerking van chemische en/of gevaarlijke stoffen: deze software is niet bedoeld voor het beheer, de controle of de operationele aspecten van chemische fabrieken of faciliteiten voor de verwerking van chemische en/of gevaarlijke stoffen. Elke storing in de software die in deze omgevingen wordt gebruikt kan leiden tot gevaarlijke chemische lozingen, explosies of milieurampen.
Transport- en verkeerscontrolesystemen: de software mag niet worden gebruikt voor de besturing, bediening of het beheer van transportsystemen, waaronder de besturing van spoorwegsignalen, metrosystemen of verkeerslichten. Storingen in dergelijke kritieke systemen kunnen tot ernstige ongelukken leiden en de openbare veiligheid in gevaar brengen.
Energienetwerk- en nutsbesturingssystemen: deze software is niet ontworpen voor de besturing of bediening van energienetwerksystemen, waaronder elektrische onderstations, besturingssystemen voor hernieuwbare energie of besturingssystemen van waternutsbedrijven. Het falen van software op deze gebieden kan leiden tot aanzienlijke stroomonderbrekingen, onderbrekingen in de watervoorziening of andere storingen in openbare voorzieningen, waardoor gemeenschappen in gevaar kunnen komen en grote schade kan worden aangericht.
Andere omgevingen met een hoog risico: alle andere kritieke infrastructuren en omgevingen waar een storing in de software kan leiden tot aanzienlijke schade aan personen of het milieu.

Gebruikersverantwoordelijkheid: gebruikers moeten ervoor zorgen dat ze het beoogde gebruik van de software begrijpen en de software niet gebruiken in een omgeving die buiten het beoogde doel valt. Het is de verantwoordelijkheid van de gebruiker om de geschiktheid van de software voor de beoogde toepassing te beoordelen, vooral in scenario's die een risico kunnen vormen voor leven, gezondheid en/of milieu.

Afwijzing van aansprakelijkheid: Invantive wijst elke verantwoordelijkheid af voor schade, letsel of wettelijke gevolgen die voortvloeien uit het gebruik of misbruik van deze software in verboden en/of onbedoelde toepassingen.

Schakel JavaScript in om deze site te bekijken.

CompanyInfo Data Model CompanyInfo Forums

Company.info SQL Driver Attributes

Belangrijke Informatie over Veiligheid en Gebruik