invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Invantive UniversalSQL Server

Release Note - Download

Invantive UniversalSQL Server 27.0, from 26.0

Build Date Description
26.0.4 22-03-2026 first build of release 26.0
27.0.54 01-11-2026 latest build of release 27.0 at the time of writing

The older state is the first build of release 26.0, not its last: later builds of 26.0 received ports of changes made for 27.0, so those changes are part of this step. The 27.0 line also contains the beta builds 26.1.x.

  • 259 enhancements
  • 152 bug fixes
  • 10 things to check before upgrading

Before You Upgrade

These changes ask for a check:

Top 25 Changes

  1. Settings files move from XML to JSON
    • Enhancement
    • action needed
    • Action needed before or after the upgrade.
  2. More work is sent to the platform: row limit, grouping, selected columns and joins
    • Enhancement
    • A query with LIMIT or TOP is limited by the platform, COUNT, SUM and other group functions are answered by the platform on supported drivers, only the columns that a query needs are requested, join conditions are forwarded, an exists condition on a child table reaches the platform, and OData platforms get shorter filters with the IN operator. Fewer rows are transferred.
  3. Joins return the correct rows
    • Bug Fix
    • A left, right or full join written without the word OUTER was executed as an inner join and lost rows. A right outer join placed columns in the wrong order, a condition in ON removed rows, a cross join dropped its right-hand side, and a full outer join that could not be answered was not reported.
  4. Correlated subqueries are supported
    • Enhancement
    • A subquery can refer to columns of the outer query, as in EXISTS, IN and scalar subqueries. A subquery without outer references is evaluated once per statement and its answer is reused.
  5. SQL Server Management Studio 20, 21 and 22 can work with the server
    • Enhancement
    • SQL Server Management Studio versions 20 to 22 can browse databases, tables, views, procedures, indexes and the table designer (read only). Scripting a view gives a clear placeholder text, and an object has one identifier everywhere. SSMS 21 and 22 variants of the same statements are both understood.
  6. DeepL driver
    • Enhancement
    • A new driver reads and writes DeepL: languages, billing, translation, writing assistance, documents, glossaries, style rules and translation memories.
  7. Parts of a PSQL block can run in parallel
    • Enhancement
    • PSQL gets a PARALLEL construct that runs branches and loop iterations side by side, SYNCHRONIZE accepts a parallel option, and the package dbms_atomic holds values that parallel branches share safely.
  8. Exact Online companies outside the service area are no longer accepted
    • Enhancement
    • action needed
    • Action needed before or after the upgrade.
  9. Loading of provider assemblies from a settings file is blocked
    • Enhancement
    • action needed
    • Action needed before or after the upgrade.
  10. Remove the LinkedIn and Loket.nl SOAP drivers and the Dynamics CRM table list
    • Enhancement
    • action needed
    • Action needed before or after the upgrade.
  11. QR code functions take one size value instead of width and height
    • Enhancement
    • action needed
    • Action needed before or after the upgrade.
  12. Data is loaded in the background while a session is idle
    • Enhancement
    • A connected session fills caches with predictable data, such as the tables read in the last fourteen days and the incremental tables of Exact Online, Freshdesk and Freshservice, using spare rate allowance. Four loads run in parallel, partitions can be chosen, and the connection monitor shows the loads.
  13. New platforms: Inspectlet, Matomo, Nextcloud and Tweede Kamer v5
    • Enhancement
    • Four new drivers read Inspectlet (websites and recorded sessions), Matomo web analytics with a package of PSQL procedures, a Nextcloud server (tables depend on the installed apps) and the Tweede Kamer open data on the new API. The earlier Tweede Kamer driver remains available. Each platform has a licence module and an icon.
  14. Invantive License Service: clearer messages, grace period and new modules
    • Enhancement
    • A licence key of the wrong type is explained, a licence service that is unavailable gets a specific message, and a licence that was valid stays in force for a grace period when the service cannot be reached. The check that prolongs a licence runs hourly. New licence modules exist for the Support Assistant, OEM use and subscription software, the built-in trial and open data keys use the new format, and text-mode products show tips about the licence in use.
  15. Big Data JSON reads files much faster and skips files that cannot match
    • Enhancement
    • Collections of NDJSON files, plain or Zstandard compressed, are streamed and only the needed columns are built. A directory gets an index with value ranges, Bloom filters and counts, so filters, counts and group-by statements read fewer files.
  16. Visma.net: new API specification, Visma Connect log-on and the Sales Order APIs
    • Enhancement
    • The Visma.net driver uses the API specification of 18 June 2026 and the new Visma Connect sign-in, and adds tables for the Sales Order APIs with server-side filtering, insert and update. Filters such as not in and not equal on a column with a fixed list of values are sent as requests for the remaining values.
  17. Exact Online incremental tables reload less often and are read faster
    • Enhancement
    • Incremental tables avoid full reloads caused by a rejected previous image or a row count guard, are read from the cache up to six times faster, and stop an incremental run when the deleted rows needed are older than the platform keeps them. The new table IncrementalEntityTypes lists the entity types that can be loaded incrementally.
  18. Support filtering and sorting of the OData model used by MCP
    • Enhancement
    • The OData data model that is built for MCP supports filtering and ordering, and carries annotations about what is supported. The model is cached and rebuilt from database metadata. Several edits during development repaired earlier edits of the same feature.
  19. Run the server as a web application with a home page and error pages
    • Enhancement
    • The server now runs as a web application next to the TDS listener. It serves a home page with version, node and request details, a robots.txt file and error pages. Several settings are now required at startup, such as the node name and the key and cache directories, and startup stops with a message when one is missing.
  20. Support prepared statements and server-side cursors for ODBC clients
    • Enhancement
    • Clients can prepare statements and open, fetch from, move in and close server cursors, as ODBC drivers do. Statement parameters are read by position or by name. Before, these calls were not available.
  21. Data containers and credentials from Invantive Credentials Server
    • Enhancement
    • A database definition can point to Invantive Credentials Server, which supplies the data containers and sign-in credentials. The log-on window and the partition menu show these containers with their own icon, errors of the server are shown with their details, and a retrieval is repeated after a time-out.
  22. IP address validation configurable with allow lists, deny lists and ranges
    • Enhancement
    • An administrator can now set the IP address validation of the web servers in the settings: use of the allow list, the deny list and Invantive Customer Service can each be switched off, extra addresses and address ranges can be allowed or denied, and the built-in default lists can be excluded. Addresses on an allow or deny list are decided before any look-up is made.
  23. Proxy and load balancer set-up through a ForwardedHeaders section
    • Enhancement
    • The way a server learns the client address behind a proxy or load balancer is now set in one section of the settings, with a choice between the Kestrel mechanism and the Invantive mechanism, the headers to follow, the number of hops, the known proxies and the allowed host names. The earlier setting that said that the server runs behind a proxy is removed. The start-up trace explains what was configured and what the framework applied.
  24. Filters no longer lose rows or evaluate wrongly
    • Bug Fix
    • A condition such as a and (b or c) could return too few rows, lower and upper case conversions and decimal constants were not sent correctly to SQL databases, NOT LIKE dropped rows that differ only in case, and x between 1 and 2 and y = 1 was read wrongly.
  25. Exact Online incremental data is no longer damaged or overwritten
    • Bug Fix
    • Users of one subscription replaced each other's incremental image, a request that ended while an image was saved could leave chunks of two versions, a refresh that only added rows was taken as unchanged, and incremental data could end up in the folder of other cache settings or ignore the disk cache settings of the statement.

All Enhancements

Changes to behaviour, platforms, drivers and settings, grouped by area.

Importance: all | 2 and higher | 3 and higher | 4 and higher | 5

Platform: all | AccountView (1) | ActiveCampaign (3) | AFAS (1) | AFAS Online (3) | Autotask (1) | Big Data JSON (1) | Brevo (2) | Bridge Online (4) | CBS (1) | Chargebee (1) | Crisp (4) | Data Cache (1) | DeepL (1) | Discourse (1) | Dropbox (1) | Dynamics 365 CRM (2) | Dynamics CRM (2) | Easyflex (1) | EDIFACT (1) | Exact Online (32) | Firebird (2) | Fortnox (1) | FoxPro (1) | Freshdesk (3) | Freshservice (2) | FTP (1) | Gripp (1) | Gripp CRM (2) | HubSpot (3) | IBM Db2 (1) | In-memory (2) | In-memory storage (1) | Inspectlet (2) | Invantive Bridge Online (1) | Invantive Business (1) | Invantive Estate (1) | Invantive Web Service (1) | ionBIZ (1) | Kadaster (1) | LinkedIn (1) | Logius COR (1) | Loket (1) | Loket.nl (2) | Magento (3) | MariaDB (1) | Matomo (2) | Mendix (1) | Microsoft Access (1) | Microsoft Dynamics CRM (1) | Microsoft Graph (1) | MySQL (10) | Nextcloud (1) | Nmbrs (2) | OData (1) | ODBC (3) | Odoo (4) | Open Archives (1) | Open Besluitvorming (1) | Oracle (14) | PayPal (2) | Pipedrive (1) | PostgreSQL (14) | Rabobank MT940 (1) | RDW (2) | Robaws (3) | Salesforce (1) | SFTP (1) | SnelStart (5) | SQL Server (13) | Stripo (2) | Teamleader (1) | Teamleader Focus (2) | TeamViewer (1) | Tixly (1) | Tweede Kamer (2) | Twinfield (7) | VIES (1) | Visma Severa (1) | Visma.net (5) | Wikipedia (1) | WMI (1) | XAA (1) | XAF (1) | Yuki (4)

13 of 411 shown.

SQL engine

Column references may carry a schema and table qualifier

A column can be written as column, qualifier.column or schema.table.column, as in SQL Server.

  • SQL Server
  • importance 3
Copying data keeps the original database data type

The data type as the database reports it is kept with a column and used for bulk insert and create table. Wide decimal columns keep their integer digits when copied to MySQL, Oracle or SQL Server.

  • Oracle
  • MySQL
  • SQL Server
  • importance 3

Platforms and drivers

Set the idle period before SQL connections are closed

A new provider attribute sets after how many seconds an idle connection to a SQL database is closed. Server products keep connections for 300 seconds by default.

  • SQL Server
  • MySQL
  • PostgreSQL
  • Oracle
  • importance 3
Support SQL Server geography, geometry and hierarchyid data types

Columns of the SQL Server types geography, geometry and hierarchyid can now be read through the SQL Server driver.

  • SQL Server
  • importance 3
Read tables with composite primary keys from SQL Server

Tables whose primary key has several columns are now known with all key columns.

  • SQL Server
  • importance 2
Register the number of rows of tables as statistic for SQL Server, MySQL and PostgreSQL

The row count that the catalogue of the database knows is registered per table, so that the engine can plan and report with it.

  • SQL Server
  • MySQL
  • PostgreSQL
  • importance 2
SQL Server driver loading is checked and reported with a clear error

The SQL Server provider now uses the Microsoft SQL Server client library by name and reports an error when the driver cannot be loaded for the operating system or processor.

  • SQL Server
  • importance 2

Performance

More work is sent to the platform: row limit, grouping, selected columns and joins

A query with LIMIT or TOP is limited by the platform, COUNT, SUM and other group functions are answered by the platform on supported drivers, only the columns that a query needs are requested, join conditions are forwarded, an exists condition on a child table reaches the platform, and OData platforms get shorter filters with the IN operator. Fewer rows are transferred.

  • ActiveCampaign
  • Bridge Online
  • Crisp
  • Exact Online
  • IBM Db2
  • Inspectlet
  • Invantive Bridge Online
  • Matomo
  • MySQL
  • ODBC
  • OData
  • Odoo
  • Oracle
  • PayPal
  • PostgreSQL
  • SQL Server
  • Tweede Kamer
  • importance 5
Lower memory use and faster processing

Encryption, compression, logging, translations, JSON reading, sorting, the in-memory driver and long-running sessions allocate less memory and use less CPU time. Creating a table from a large result streams the rows, and several string functions run faster.

  • Exact Online
  • In-memory
  • MySQL
  • Oracle
  • PostgreSQL
  • SQL Server
  • XAF
  • importance 3

All Bug Fixes

Defects of the older release that are repaired.

SQL engine

Filters no longer lose rows or evaluate wrongly

A condition such as a and (b or c) could return too few rows, lower and upper case conversions and decimal constants were not sent correctly to SQL databases, NOT LIKE dropped rows that differ only in case, and x between 1 and 2 and y = 1 was read wrongly.

  • Microsoft Access
  • SQL Server
  • importance 4
Aggregates pushed down to databases return the right data types

A count pushed down to a database platform came back with the type of that platform, which the engine did not accept for some platforms. A platform limited to one connection also refused a second statement on the same session. Both are handled.

  • SQL Server
  • Oracle
  • Firebird
  • importance 2
Repair errors of parallel background reads being missed

Errors in parallel reads were not always reported to the statement.

  • SQL Server
  • importance 2

Platforms and drivers

SQL Server: driver update to Microsoft.Data.SqlClient 7.0.2

The SQL Server driver uses version 7.0.2 of the Microsoft client library, which repairs an issue with bulk insert and create table. The first 26.0 build used 7.0.0.

  • SQL Server
  • importance 2

What It Builds On

Kind Name From To
invantive component Invantive UniversalSQL Server 26.0.4 27.0.54
invantive component Invantive(R) Basics 26.0.4 27.0.92
invantive component Invantive(R) Cloud API Shared 26.0.4 27.0.92
invantive component Invantive(R) SQL for Core 26.0.4 27.0.92
invantive component Invantive(R) SQL 26.0.4 27.0.92
invantive component Invantive(R) Web Core Library 26.0.4 27.0.92
build tool Invantive Deploy 26.0.4 27.0.92
third party summary

More Information

How This Note Was Made

  • For all products together 28 items whose changed lines are 50 to 70 % in the first build of 26.0 and 23 items that a content check would have left out were read against that build; the items that apply to this product are kept or left out on that reading.
  • Range: commits of origin/release-27.0 that are not reachable from the first build of release 26.0 (stamp 26.0.4, per repository). Commits that were ported to later builds of 26.0 are therefore included.
  • For a product that does not offer SQL to its users, items of the shared libraries outside the areas installation, licensing, security and diagnostics, and items about one platform, are left out and counted as internal.
  • The commits are the ones of the range that touch a project of the product; each commit was classified once, for all products, and the items of a product are the items that contain such commits.
  • Version stamp commits of the build pipeline are left out.
  • A change whose changed lines are for 70 % or more already in the first 26.0 build is left out; items between 50 % and 70 % and all such exclusions were checked by reading the code of that build.
  • A bug fix whose repaired lines were written by another commit of the same range is merged into its feature or left out.
  • Texts were written from the commit messages and from the changes themselves; items carry a confidence.
  • 1184 links between a change and a source commit are recorded.
  • 74 exclusions are recorded in the audit of the note.