Specifications for all known databases. Group of databases. Databases are typically grouped per used company, but other groupings are possible too. Optional label of the default database to use when no other database is presented by the user. The label consists of the group name, a backslash ('\') and the database name. Not all products cover the use of default database. The version of the settings.xml format. New versions typically add new XML elements and attributes, but remain backward compatible. The current version is 5. The Version attribute was introduced with version 3 of the settings.xml format. Whom updated the version of the settings.xml last. When the version of the settings.xml was updated last (UTC). The name of the machine that updated the version of the settings.xml last. Obsoleted. Obsoleted. Obsoleted. A database. Each session on an Invantive product connects to at most one database at the same time. Optional unique ID of the database group. Used to identify a database group across name changes. Required name of this database group. The name can not contain a backslash. Some Invantive applications allow the use of non-unique names, but it is recommended to choose unique names for usability. Optional numeric sorting order of the database group. Database groups are typically presented to an end user sorted ascendingly according to sorting order. Optional name of pre-defined file with icon 32x32 within Resources folder of Invantive Producer. Optional one-line description of the database group. Optional comment on the database group. Optional multi-line description. Machine this object was created on. User that created this object. Date when this object was created (UTC). Additional connector to load into memory when using the database. Direct connection to a data container provided by a data platform using a locally installed connector. Connection to a data container provided by a data platform through a remote server running Invantive Web Service. An alternative set of connection data to access the data containers of the database in case the preferred route is not available or reliable. Date when this object was created (UTC). Optional name of pre-defined file with icon 16x16 within Resources folder of Invantive Producer. Obsolete. Whether to show the password and whether it is changeable by the user. Replaced by data container specific settings. Machine this object was created on. Whether the database definition was created manually. Set to true when edit by user. Setting to true avoids replacement of database properties by discovery. User that created this object. Obsolete. Optional encrypted Invantive Data Dictionary connection settings. Optional Invantive Data Dictionary connection settings. Obsolete. Replaced by data container specific settings. Obsolete. Replaced by data container specific settings. Optional encrypted Invantive Data Cache or Data Replicator connection settings. Whether to enforce use of native database language instead of Invantive SQL. When the database was last used (UTC). Optional alias of a deviating data container to retrieve IUID from. Optional Invantive Data Cache or Data Replicator connection settings. Whether SQL tracing is allowed. Optional comment on the database. Numeric sorting order of the database. Databases are typically presented to an end user sorted within a group ascendingly according to sorting order. Whether the database is starred and should be shown as preferred in a user interface. Required name of this database. The name can not contain a backslash. Some Invantive applications allow the use of non-unique names, but it is recommended to choose unique names for usability. Optional one-line description of the database. Optional multi-line description. Obsolete. Replaced by data container specific settings. Obsolete. Replaced by data container specific settings. Obsolete. Replaced by data container specific settings. Obsolete. Replaced by data container specific settings. Obsolete. Replaced by data container specific settings. Obsolete. Replaced by data container specific settings. Obsolete. Replaced by data container specific settings. Obsolete. Whether to show the user logon code and whether it is changeable by the user. Replaced by data container specific settings. Connector attribute value assignments. Required unique order in which the provider is tried. A connector with a higher order number is asked first to handle a request. Name of the file containing the class, for example 'System.Data.OracleClient'. Name of the .net class for the connector. Optional comment on the additional connector. User that created this object. Machine this object was created on. Date when this object was created (UTC). Required unique code of the connector attribute. Value to assign to the connector attribute. Optional connection string to pass to the connector. Optional encrypted connection string to pass to the connector. Whether to allow rewriting the connection string values, such as user name, password or attribute values. Whether to allow connection pooling on connections. A data container stored on a data platform. Non-unique numeric order of the data container used for sorting data containers of a database. User that created this object. Machine this object was created on. Date when this object was created (UTC). Optional multi-line description of the data container. Optional comment on the data container. Optional alias of the data container, unique within the database. Required code of the connector to use for connection. Optional default user logon code. Whether to show the user logon code and whether it is changeable by the user. Optional default password. Optional password label. Optional password hint. Optional user logon code label. Optional user logon code hint. Whether to show or hide the password and whether it can be edited. Required URL of the Invantive Web Service to use. Message encoding of the Invantive Web Service to use, either 'text' or 'binary'. Whether to apply compression, one of 'Auto', 'True' or 'False'. Optional URL to ping for check whether the connection is alive. Optional maximum test duration in milliseconds when checking whether the connection is alive. -1 means forever Whether to check if the connection is alive before really logging on to the web service. Full remote database name in the format GROUP\NAME. Whether to allow rewriting the connection string values, such as user name, password or attribute values. Direct connection to a data container of a data platform using a locally installed connector. Connection to a data container of a data platform through a remote server running Invantive Web Service. Whether values are editable by an end-user, read-only visible or hidden. Approach to use for authentication. Use the default except when using Invantive business solutions with a middle-tier. Use database authentication mode. Middle-tier specific authentication. Used in combination with Invantive business solutions that provide a middle-tier, such as Invantive Estate and Invantive Studio. Instead of authenticating on the database layer with the provided credentials, a connection is first made using default credentials to the database with severely restricted privileges and then the middle-tier is used to authenticate and open up the full functionality. Default authentication model, used for most applications.