Written by

Program Manager at InterSystems
InterSystems Official Daniel Palevski · Feb 3

Third InterSystems IRIS, InterSystems IRIS for Health, and HealthShare Health Connect 2026.1 Developer Preview available

The third developer previews of InterSystems IRIS® data platform, InterSystems IRIS® for Health, and HealthShare® Health Connect 2026.1 have been posted to the WRC developer preview site.  Containers can be found on our container registry and are tagged latest-preview.

These developer previews includes the dropping of Mac Intel support starting from 2026.1.0, and the adding back of Windows Server 2019 support to 2026.1.0.

Initial documentation can be found at these links below:

The documentation links currently serve as placeholders and will be updated as we get closer to the final build and have more details to share. Here are some notable additions to the 2026.1 documentation:

Because this is an early Developer Preview, some content is still in progress, and we’ll provide full documentation as features are finalized. We appreciate your patience and feedback during this phase!

Availability and Package Information

This release comes with classic installation packages for all supported platforms.  For a complete list, refer to the Supported Platforms document.

Installation packages and preview keys are available from the WRC's preview download site or through the evaluation services website (tick the "Show Preview Software" box).

Comments

Benjamin De Boe · Feb 4

We found a small issue affecting some Vector Search queries that may lead to a runtime error when your vector search query uses aliases to shorten or disambiguate table names. The problem can be worked around by rewriting your query to avoid using aliases. A fix for this issue will be included in the next preview kit, due in two weeks.

We also identified a separate issue with unintended changes to DSTIME behaviour, and recommend DSTIME users to skip this preview. The next preview kit will restore the original DSTIME behaviour.

0
Benjamin De Boe  Feb 6 to Enrico Parisi

extended is not the same as unlimited :-)

We're moving from 32-bit block numbers to 40-bit block numbers, which means the max size for a database with 8k block size is 8PB. Obviously, those are huge amounts of data, and we strongly recommend against just stashing that all in a single IRIS.DAT file,, if your file system permits such files at all. Multivolume database support already helps you spread data across multiple physical files (opaquely), and the new Table Partitioning support (experimental in 2026.1) helps you spread table data across multiple databases. 

If you wonder why we stuck with 40 bit numbers rather than a power of 2: we were able to reuse a few available bits in the current block header format, meaning you can transparently and instantly upgrade to this Extended Database Format without having to migrate your almost-32TB database to a new block header format. And 8PB is quite large already...

0