System Requirements

Summary

MFSQL Connector is available in two active releases, each supporting different versions of SQL Server and M-Files:

Release 4

  • SQL Server: 2016–2021 (Express or Standard)

  • M-Files: Version 22.5 to 25.04 (On-premise or Cloud)

  • Architecture: M-Files Classic Desktop and older versions on the server

Release 5

  • SQL Server: 2022–2025 (Express or Standard)

  • M-Files: Version 25.5 and later (On-premise or Cloud)

  • Architecture: New M-Files desktop and New Web architecture

Detailed Requirements

User Requirements

  • 1 named user dedicated to MFSQL Connector with Vault administrator rights

  • Recommended: Assign a named M-Files authentication user license.

Package Installation

  • Release 4 requires Windows OS with 32-bit SQL connection protocol.

  • Release 5 requires 64-bit protocol.

  • PowerShell v5+ must be installed and enabled on both SQL and M-Files servers.

  • Manual installation is possible if PowerShell is not enabled.

M-Files Database

  • Supports both Firebird and SQL vaults.

M-Files Installation

  • Target vault must be pre-existing.

  • M-Files client must be installed on the SQL Server.

  • M-Files desktop client is optional on the M-Files Server.

  • Each vault requires a dedicated Connector database.

  • Recommended: Separate environments for Development and Production.

  • Recommended: Use a naming convention to link databases to vaults for example ‘’MFSQL/_<VaultName>/_PROD/Dev’’.

Connector Database

  • Supported: SQL Server 2016+ (Express, Standard, Enterprise)

  • Release 5 supports SQL Server 2022 and beyond.

  • Express edition limitations: No agents, performance constraints.

  • SQL Server must be configured with Mixed Mode Authentication.

M-Files to SQL Connection

  • Same domain: Uses ODBC or web service.

  • Different domain / Cloud: Requires web service app deployment. Refer to Installing the Web API for more information.

Database Size Allocation

  • Default size and file locations used is usually sufficient.

  • Large vaults may require additional space for Class Tables.

  • Implement log table purging to prevent excessive growth.

  • Default recovery model is Full; consider switching to Simple to limit log file growth.

SQL Server Configuration

  • Optional: Database Mail for error notifications.

  • Error messages available via MFLog table if Database Mail is not used.

  • Recommended: Enable SQL Agent for scheduled tasks.

  • Express edition does not support SQL Agent; use Windows Task Scheduler as an alternative.

  • Note: SQL Agent is not available in the Express edition.

  • Required: Enable SQL CLR for advanced functionality.

.NET / Runtime

  • Release 4: .NET Framework 4.6.

  • Release 5: .NET 8 (or later, where supported).

  • Installer is TLS 1.2 compliant.

Reserved Words

Avoid using the following reserved words as M-Files property names:

  • Process, Process ID

  • GUID, ID

  • Update, Update ID

  • LastModified, FileCount

  • State, State_ID, State ID

Tip

Rename property 39 State to Workflow State or use StateID to avoid conflicts.

Class Table Names must not match default table names created during installation (e.g., Process, or Module).

Assumptions and Constraints

  • Intended for experienced consultants or developers familiar with M-Files configuration and T-SQL.

  • Not designed as an end-user application.

  • SQL access is governed by SQL Server permissions, not M-Files permissions.