Migration to 1.26+

In order to reduce the amount of potential deadlocks for MSSQL, the following settings must be enabled for macma-core and keycloak databases:

ALTER DATABASE [master-data-database] SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE [master-data-database] SET READ_COMMITTED_SNAPSHOT ON WITH NO_WAIT

ALTER DATABASE [keycloak] SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE [keycloak] SET READ_COMMITTED_SNAPSHOT ON WITH NO_WAIT

Azure SQL already has these settings enabled by default

The READ_COMMITTED_SNAPSHOT setting can only be applied if not other connections to the database exist. There are various options to enforce that:

limit database to mode RESTRICTED_USER (rather than SINGLE_USER) temporarily before reverting to MULTI_USER using:
```
ALTER DATABASE [master-data-database] SET <mode> WITH ROLLBACK AFTER 30 SECONDS
```
shut down all applications;
add WITH ROLLBACK IMMEDIATE instead of WITH NO_WAIT to force a rollback of all active transactions;
use database failover to replicas to reconfigure them one by one.

The state of these settings can be checked with the following query:

SELECT name, snapshot_isolation_state, is_read_committed_snapshot_on FROM sys.databases WHERE name IN ('master-data-database', 'keycloak')

Keycloak

In an oracle database setup Keycloak requires the execute grant on DBMS_LOB.

The name of the stateful-set in the helmchart was changed from keycloak to keycloak-22 (and consequently the name of the generated kubernetes stateful-set is now keycloak-22-statefulset).
This is important in case there are any helm configurations overridden for Keycloak for a specific installation.