Known issues

When a connection uses Microsoft Entra authentication, SQL Multicast signs in through the default credential flow only. The other Entra authentication modes are not offered in the connection dialog.

This is a deliberate deferral, not an oversight, and there is no date for the other modes yet. If you need one of them, tell us through the contact form, because knowing who is waiting for what decides the order.

The SQL formatter runs with its built-in defaults, and Settings does not yet expose its options. The defaults are described in the editor chapter of the documentation.

If a default does not suit how your team writes SQL, tell us which one through the contact form.

Builds published on the beta channel are not code-signed. Windows may warn you about an unrecognized publisher the first time you run the installer, and some managed environments may block it until IT allows it.

Code signing is not in place yet; the beta channel is a temporary way of distributing the app. If your organization needs a signed build before it can install the app, contact us through the contact form so we know.

There is no way to wrap a script, or a run, in a transaction that SQL Multicast manages for you. This is deliberate.

A target's connection is disposed when the run finishes with that target. Disposing a connection rolls back anything still open and releases its locks, so a script that leaves a transaction open does not keep it. If you want a transaction to commit, the script has to commit it.