Use the "Search" option in the left menu to search for a specific term such as the table or column description. When you already know the term, please use the "Index" option. When you can't find the information needed, please click on the Chat button at the bottom or place your question in the user community. Other users or Invantive Support will try to help you to our best.
The Invantive SQL data dictionary contains the metadata of your current environment. For example, the view SystemTables@DataDictionary contains every available table and view in the current database. Besides object definitions also actual execution information is available in views. For example, the view SystemSqlArea@DataDictionary contains all executed and cached Invantive SQL statements. The data in the data dictionary views is generated dynamically by Invantive SQL from the runtime environment. Changing data in the data dictionary views is not possible.
Invantive SQL is available on many user interfaces ("clients" in traditional server-client paradigma). All Invantive SQL statements can be exchanged with a close to 100% compatibility across all clients and operating systems (Windows, MacOS, Linux, iOS, Android).
The clients include Microsoft Excel, Microsoft Power BI, Microsoft Power Query, Microsoft Word and Microsoft Outlook. Web-based clients include Invantive Cloud, Invantive Bridge Online as OData proxy, Invantive App Online for interactive apps, Online SQL Editor for query execution and Invantive Data Access Point as extended proxy.
For technical users there are command-line editions of Invantive Data Hub running on iOS, Android, Windows, MacOS and Linux. Invantive Data Hub is also often used for enterprise server applications such as ETL.
The SQL driver for Data Dictionary does not support partitioning.
An introduction into the concepts of Invantive SQL such as databases, data containers and partitioning can be found in the Invantive SQL grammar.
The configuration can be changed using various attributes during log on and use. A full list of configuration options is listed in the driver attributes.
The catalog name is used to compose the full qualified name of an object like a table or view. The schema name is used to compose the full qualified name of an object like a table or view. On Data Dictionary the comparison of two texts is case sensitive by default.
Driver code for use in settings.xml: DataDictionary
Recommended alias: dd
06-04-2021 14:36 Version 20.1.393-BETA+3152