Release notes of CBS
Driver Release Note - Cloud
CBS driver 27.0, from 26.0
| Build | Date | Description |
|---|---|---|
26.0.4 |
22-03-2026 | first build of release 26.0 |
27. |
10-11-2026 | latest build of release 27.0 at the time of writing |
Data models compared: 26.0.340-PROD+6295 and 27.0.6-PROD+6293.
The older end is the first build of release 26.0, not its last, because later builds of 26.0 received ports of changes made for 27.0. The data model of a release is the model that a later build of the same release generated.
- 9 changes
- 2 can break a statement
- 0 groups not available
This Note
Groups
- Data model 2
- Provider attributes 3
- Capabilities 0
- Performance 1
- Bug fixes 1
- Enhancements 2
- Log-on and platform 0
More
What Changed, by Group
Every change is in one group: the group answers the question that you ask before you upgrade.
- Data model
- 2
- Do my statements and views still work?
- Provider attributes
- 3
- 1 can break a statement
- Do I have to change my connection string, provider file or settings?
- Capabilities
- 0
- What can the driver do with a table?
- Performance
- 1
- Is it faster, and does it call the platform less?
- Bug fixes
- 1
- Is the defect that I met repaired?
- Enhancements
- 2
- 1 can break a statement
- What can I do now that I could not?
- Log-on and platform
- 0
- Do I have to log on again, or change something because of the platform?
Download Changes as CSV | Data Model of CBS
Before You Upgrade
These changes can stop an existing statement, view, connection string or script from working:
- Attribute maximum-acceptable-metadata-error-count is removed
- Check statements, views and scripts that use it before the upgrade.
- Connection attribute for acceptable metadata errors renamed to a shorter name
- Replace maximum-acceptable-metadata-error-count by max-acceptable-metadata-error-count in connection strings and provider files.
Top 6 Changes
Changes that can break a statement first, then by importance. Columns are summarised per table in the data model.
- Attribute maximum-acceptable-metadata-error-count is removed
- Provider attributes
- Breaks an existing statement or script.
- Connection attribute for acceptable metadata errors renamed to a shorter name
- Enhancements
- Breaks an existing statement or script.
- Metadata of the CBS catalogue is read in parallel and a row limit is sent to the platform
- Performance
- Importance 3 of 5.
- Attribute max-acceptable-metadata-error-count is added
- Provider attributes
- Importance 3 of 5.
- Static throughput figures for CBS are available for planning and estimates
- Enhancements
- Importance 2 of 5.
- No crash when CBS returns an empty or incomplete catalogue entry
- Bug fixes
- Importance 1 of 5.
Data model
Do my statements and views still work? Tables, views, table functions, columns, parameters, keys, code values, packages and procedures that appear, disappear, are renamed or change type.
- 2 changes
- model files
Columns
0 added, 0 removed, 2 changed, in 1 tables.
CBSNL.Native.NATIVEPLATFORMSCALARREQUESTS: 0 added, 0 removed, 2 changed
CBSNL.Native.NATIVEPLATFORMSCALARREQUESTS: 0 added, 0 removed, 2 changed~DURATION_MS(database_data_type:int64→double)~DURATION_MS(dotnet_data_type:int64→double)
Provider attributes
Do I have to change my connection string, provider file or settings? Attributes of the connection and settings of the driver that appear, disappear or change default or place where they can be set.
- 3 changes
- model files
Attribute maximum-acceptable-metadata-error-count is removed
A connection string or provider file that sets the attribute is rejected after the upgrade. This is a rename: the same setting (default 50) now has a shorter name.
What to Do
Check statements, views and scripts that use it before the upgrade.
- can break a statement
- importance 4
Engine-wide connection attributes change
28 attributes added, 2 removed and 5 settings of attributes changed. These attributes belong to the SQL engine and exist for every driver; the Query Tool notes describe them.
- importance 2
Attribute max-acceptable-metadata-error-count is added
Can be set from connection string, SET statement, provider file. Default 50. This is a rename: the same setting (default 50) now has a shorter name.
- importance 3
Capabilities
What can the driver do with a table? Whether a table or table function can be selected from, inserted into, updated and deleted from.
- 0 changes
- model files
No changes in this group.
Performance
Is it faster, and does it call the platform less? Paging, batching, caching, filters and projections sent to the platform, fewer requests, less memory.
- 1 changes
- commits
Metadata of the CBS catalogue is read in parallel and a row limit is sent to the platform
The list of CBS data sets and their metadata is now retrieved through a pipeline that reads several catalogues and data sets at the same time, with less memory spent on JSON. A row limit in a query is now sent to CBS, so that large tables can be read with a limit; without it CBS can answer with an error. A cancelled metadata run is no longer stored as a complete catalogue.
- importance 3
- confidence medium
Bug fixes
Is the defect that I met repaired? Wrong or missing rows, wrong values, crashes and wrong messages, repaired in a release line that had the defect.
- 1 changes
- commits
No crash when CBS returns an empty or incomplete catalogue entry
Reading the CBS catalogue no longer fails when CBS answers without a list of data sets or when a data set has no output status.
- importance 1
- confidence medium
Enhancements
What can I do now that I could not? New functions and options that are not a table or a column.
- 2 changes
- commits
Connection attribute for acceptable metadata errors renamed to a shorter name
The attribute that sets how many metadata errors are tolerated while reading the CBS catalogue is now called max-acceptable-metadata-error-count (default 50). A connection string or provider file that still uses the old name maximum-acceptable-metadata-error-count must be changed.
What to Do
Replace maximum-acceptable-metadata-error-count by max-acceptable-metadata-error-count in connection strings and provider files.
- can break a statement
- importance 3
- confidence medium
Static throughput figures for CBS are available for planning and estimates
The driver now carries measured average latency and read speeds for CBS and for its data sets. These figures help the engine and tools such as the progress panel to estimate how long a query takes.
- importance 2
- confidence medium
Log-on and platform
Do I have to log on again, or change something because of the platform? Log-on and token handling, scopes and permissions, a new version of the platform API, retired endpoints and changed limits.
- 0 changes
- commits
No changes in this group.
In Numbers
Objects of the data model at both ends of the step.
| Objects | 26.0 | 27.0 | Change |
|---|---|---|---|
| tables | 53,071 | 53,071 | +0 |
| views | 1 | 1 | +0 |
| table functions | 0 | 0 | +0 |
| columns | 758,384 | 758,384 | +0 |
| function parameters | 0 | 0 | +0 |
| attributes of driver | 1 | 1 | +0 |
| tables that can insert | 1 | 1 | +0 |
| tables that can update | 0 | 0 | +0 |
| tables that can delete | 0 | 0 | +0 |
More Information
- Data model documentation of the driver
- Questions and answers on the forum
- Invantive Cloud page of the driver
- Documentation of the platform
- All release notes
How This Note Was Made
- 2026-11-01T12:44:03.1958953Z
- 2026-11-01T12:31:45.7755023Z
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Commit items were classified by one reader; the model changes are derived and need no reading.
- Commits: the commits of the driver directory in the range that have no equivalent patch in the older state, without merges and version stamps; each was classified by reading its message and change.
- Model: the NDJSON files of data-models/database of the workspace of each release are compared record by record; only fields that both models have are compared, and texts are counted, not listed.
- A model generated from a later build of the same release (for example 26.0.340 for 26.0) stands for the release.
- 10 links between a change and a source commit are recorded.