Licensing

License management use M-Files licensing method for vault applications. A license file (.lic file) is issued for a specific type of license for a specific period. The license is installed using M-Files Admin. The license is per M-Files server and can be used across all vaults on that server. The license is issued for a specific M-Files server and will not operate on any other M-Files server. The license is validated when the vault is started. If the license is invalid, then the MFSQL Connector will not operate.

License types

  • Trial license:

    • 30 days only.

    • Expires on license end date.

  • Rental license:

    • Monthly

    • Expires on the end date of the rental.

  • Subscription:

    • 1 year maximum.

    • Expires on license end date.

  • Test and QA

    • A free test or QA license is available for a subscription license.

    • Follow the same rules as the subscription license

  • NFR license:

    Issued in terms of reseller agreement.

License conditions

  1. The license is per M-Files server and can be used across all vaults on that server. The license is issued for a specific M-Files server and will not operate on any other M-Files server.

  2. The license is subject to the following conditions: - License is per M-Files server and can be used across all vaults on that server - License is issued for a specific M-Files license and requires the M-Files serial number to operate - License for a cloud installation does not include the M-Files license number. - License is issued for specific modules and is subject to the order of the license. - Only valid with designated M-Files server. - Separate license files are issued for Database File Connector and MFSQL Connector

  3. The number of M-Files user licenses (named and concurrent) on the M-Files server determines the MFSQL licensing bracket (e.g., 1–49; 50–200, etc.). Read-only licenses are excluded from the count.

  4. The usage of specific functions and features in MFSQL Connector (as outlined in the functional overview) determines the module (e.g., Data Exchange or Integration).

  5. The number of vaults on the M-Files server is not restricted.

  6. Separate M-Files servers used for replication, backup, or any other vaults are not taken into account as long as no MFSQL Connector connection to the vaults on these separate servers is used.

  7. The number of users assigned to the vaults (irrespective of whether the vaults are using MFSQL Connector or not) is not relevant.

  8. The number of SQL Servers connected to the M-Files Server is not restricted.

  9. One MFSQL Connector license for a separate M-Files Server and serial number, exclusively used for testing and prototyping, is included at no additional cost.

  10. 30 days’ notice is required for cancellation of subscription license.

  11. The license must be renewed before the expiry date to prevent an outage of service. 30 days before the expiry date an email notification will be sent to the main support contact defined in the MFSettings table.

For questions about licensing or to request a quote, contact support.

Installing the license is covered in License management (Post-Install).

The use of MFSQL Connector is subject to the license agreement. See MFSQL Connector License Agreement. Installing the software indicates acceptance of the license agreement.