Introduction to MFSQL

• Introducing MFSQL Connector
• System Requirements
• MFSQL Connector modules
• Functional Overview
• Practical tips and Use Cases
• Licensing
• Installing MFSQL Connector

Changelog

Changes to MFSQL Connector are included in Version Control.

Glossary

MFSQL Connector

Laminin Solutions’ integration product that synchronizes and integrates M‑Files with Microsoft SQL Server using ODBC or an HTTPS Web API.

M-Files

An enterprise content management (ECM) platform that stores information in a repository called a vault.

Vault

An M‑Files repository that contains objects, metadata, and configuration.

Vault Application (VApp)

A packaged extension for M‑Files installed into a vault; built on the M‑Files VAF.

VAF (Vault Application Framework)

M‑Files’ .NET framework for building and running vault applications.

UIX v2 (User Interface Extensions v2)

The New Desktop extension model used by MFSQL Connector for the Context Menu integration.

Context Menu

The M‑Files client menu actions that trigger MFSQL Connector operations (via ODBC or Web API).

Web API

The MFSQL Connector HTTPS endpoint (hosted on IIS) used for cross‑domain/cloud scenarios where direct ODBC is not viable.

ODBC (Open Database Connectivity)

A standardized interface used by MFSQL Connector to connect the VAF to SQL Server.

IIS (Internet Information Services)

Microsoft’s web server used to host the MFSQL Connector Web API with HTTPS.

TLS/SSL

Transport Layer Security (and the older SSL) protocols that provide encryption for HTTPS; requires a valid certificate in IIS.

SQL Server Agent

The SQL Server job scheduler used to automate procedures. Not available in SQL Server Express.

SQL Server Express

The free SQL Server edition without SQL Server Agent; MFSQL provides PowerShell utilities for scheduling.

SSIS (SQL Server Integration Services)

Microsoft’s ETL platform. Some advanced automation or examples may leverage SSIS on non‑Express editions.

CLR (Common Language Runtime)

The .NET runtime inside SQL Server enabling CLR functions and procedures.

SQL Assembly

A .NET assembly registered in SQL Server and used by MFSQL Connector for certain operations.

TDS (Tabular Data Stream)

The wire protocol used by SQL Server for client communication.

gRPC

A high‑performance RPC protocol; M‑Files Server cloud endpoints may expose gRPC/HTTPS.

GUID

Globally Unique Identifier; used by M‑Files to uniquely identify objects, classes, and properties.

ObjID (Object ID)

The M‑Files internal numeric identifier for an object within a vault.

Class table

A SQL table representing an M‑Files class that stores synchronized object metadata.

Value list

An M‑Files lookup list of permissible values referenced by properties.

Metadata mapping

Linking M‑Files properties to SQL columns to enable synchronization.

Metadata synchronization

The process of updating SQL from M‑Files and vice versa to keep metadata in sync.

Staging table

A SQL table used to load or transform data before final import/export during integrations.

Audit history (Object history)

Records tracking object changes and versions used for troubleshooting and reporting.

New Desktop

The modern M‑Files client UI required by the Connector’s UIX v2 features.

PowerShell

Windows scripting language used by MFSQL tools for installation, packaging, and scheduling.

Windows Integrated Security

Authentication using Windows accounts/SSPI for file shares, SQL Server, and services.

MFSQLConnect (SQL login)

The default SQL authentication user created for the Connector in the MFSQL database.

MFSQLConnect_db (database role)

A database role granting required permissions to the MFSQLConnect login.

On‑premises

Deployment where M‑Files and SQL Server run on local infrastructure.

Cloud/hosted

Deployment where M‑Files and/or the Web API run in the cloud; typically uses HTTPS instead of direct ODBC.