High availability (SQL cluster)

MFSQL Connector can be used in a high availability SQL Server cluster. To install and upgrade MFSQL Connector the following additional steps and considerations should be taken into account when using a SQL cluster.

Prerequisites

  • Same M‑Files Desktop version on all cluster members

  • Disable auto-upgrades of M‑Files on all members

Steps

  1. Install MFSQL on the primary node. Alternatively, the manual-installation-using-scripts method can be used.

  2. Copy c:MFSQLAssemblies from primary to each member node after first installation and after each upgrade

Notes

  • SQL installation replicates automatically across nodes; you don’t re-run installer on every member

  • Schedule quarterly upgrades for M‑Files and MFSQL Connector and do not configure M-Files for auto-upgrade

  • Automatic assembly reload is per-node. Since MFSQL Connector 5.13.38.82, each cluster member independently detects its own M-Files version via the registry and reloads Interop.MFilesAPI automatically — the WMI Event Alert reacts within seconds, with a daily Agent-job fallback on each node. The manual copy step above remains necessary because each node needs its own copy of the assembly files in AssemblyInstallPath; running spMFUpdateAssemblies manually on each node afterward is optional — needed only on SQL Server Express members (no SQL Agent) or if a node’s automatic reload has not yet run. See M‑Files API version and CLR assembly updates.