Please enable JavaScript to view this site.

Navigation: » No topics above this level «

In-Memory Storage SQL Driver


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.

Session-specific in-memory database.

The In-Memory Storage driver covers 28 tables and 304 columns.

In-Memory Storage Clients

Invantive UniversalSQL is available on many user interfaces ("clients" in traditional server-client paradigma). All Invantive UniversalSQL 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.

The In-Memory Storage Power BI connector is based on the Invantive UniversalSQL driver for In-Memory Storage, completed by a high-performance OData connector which works straight on Power BI without any add-on. The OData protocol is always version 4, independent whether the backing platform uses OData, SOAP or another protocol.

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 In-Memory Storage does not support partitioning.

An introduction into the concepts of Invantive UniversalSQL such as databases, data containers and partitioning can be found in the Invantive UniversalSQL 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 In-Memory Storage the comparison of two texts is case sensitive by default.

Changes and bug fixes on the In-Memory Storage SQL driver can be found in the release notes. There is currently no specific section on the Invantive forums for In-Memory Storage. Please reach out to other users of In-Memory Storage by leaving a question or contact request.

Driver code for use in settings.xml: InMemoryStorage

Alias: inmem

Recommended alias: imy

07-10-2022 13:03 Version 22.0.384-PROD+3618