connector kept looking in the old place. Syncing stopped. Nobody noticed until a job failed or a customer called support.

That’s exactly the problem we set out to fix in MFSQL Connector Release 5.

MFSQL Connector now automatically detects M-Files updates and reloads itself accordingly. In real‑world testing the whole cycle (detect, reload, resume) finished in about four seconds. No one needs to log on to the SQL Server, no one needs to remember a post‑upgrade checklist step, and downtime is reduced to almost nothing.

Just to be safe, we’ve also added a daily check that catches any updates the immediate, ongoing detection might miss. With this feature, you’ll be doubly protected against a missed update.

This change might seem small, but it’s a small change with a big payoff: fewer interrupted syncs, fewer support calls, and less manual work for admins.

Important Note for SQL Server Express Users

There’s one important limitation to this update: the automatic detection relies on SQL Server Agent, which is not included with SQL Server Express. If you run Express, the connector cannot perform the automatic reload. Express customers still need to run a single manual step after an M‑Files upgrade to restore the connection.

Other Fixes in this Release

In addition to the auto-update, we’ve also implemented some targeted fixes in this release that improve the reliability of our software:

• Licensing checks: MFSQL Connector now has more robust and accurate validation to avoid false failures.
• History handling: Our software now creates cleaner, more consistent recording of history entries.
• Scheduled jobs: We’ve improved MFSQL Connector’s stability and correctness, especially during background tasks.

What To Do After Upgrading

Here are some tasks that should be on your to-do list once you upgrade to MFSQL Connector Release 5:

• If you run Standard or Enterprise: Make sure SQL Server Agent is enabled so the automatic detection works.
• Monitor logs briefly: Confirm the connector detected the change and reloaded successfully. The whole cycle should be visible in the logs and completed in seconds.
• Test in staging for big upgrades: If you’re planning a large migration or coordinated upgrade, run a test to verify behavior and measure any performance impact.

This MFSQL Connector release removes a manual step that used to be a common source of downtime, and it bundles fixes that make the connector more reliable every day. For most customers, upgrades will now be invisible from a syncing perspective—which is exactly how upgrades should feel.

If you manage M‑Files and SQL Server, this update is one of those small operational improvements that pays for itself in fewer late‑night support calls and less firefighting. The more small tasks you automate, the lighter the workload on you and your staff.

Looking to Implement or Upgrade MFSQL Connector?

If you’re searching for a way to edit your M-Files software through simple SQL tools, MFSQL Connector is the perfect solution for you. Learn more about how it works here.

If you’re an existing customer and would like support while upgrading your MFSQL Connector, please contact us! We want to make sure you always have exactly what you need in order to get the most out of our powerful and flexible software.