Connector Database

• Using CLR
  • SQL Server configuration for CLR
  • Architecture of CLR Integration
    • Reliability (Safety)
    • Scalability
    • Performance
    • Type safety verification
    • Application domains
    • Code Access Security (CAS)
  • Application of CLR in stored procedures
  • Benefits of using CLR
  • Securing the use of CLR
    • CLR Integration Security
• M-Files API version and CLR Assembly update
  • Prerequisites and security
  • Troubleshooting after M-Files upgrades

The Connector requires a SQL Server database that has a one‑to‑one relationship with a vault.

The database is automatically installed by the installation package. This database is completely separate from M-Files’ own databases (SQL or Firebird).

Warning

The Connector should NEVER be installed into the M-Files vault SQL database. Contact support if the deployment was accidentally pointed to the vault database.

The database will be used exclusively for the Connector and contain only one vault. Name the database to include a clear reference to both Connector and vault. We recommend the naming convention MFSQL_VaultName.

Size

This database will contain a replica of the metadata structure of the specific M-Files Vault. These tables are generally small. It will also have all the class tables that is applied in the special application. The number of tables and record volume depends on the special application but is generally not very large.  The size of these tables will depend on usage and the number of records in the classes.  Note that these tables does not include file content which further restricts the size of tables.

The largest tables in the database is likely to be the logging tables and class tables.

When sizing and monitoring the growth of the database it is important to note the log files. MFUpdateHistory in particular is likely to grow substantially, especially with high transaction volumes between M-Files and SQL. This table contains XML records of every update.

Access Security

The Connector requires a login account that can access the database. Grant the following rights to the user: EXECUTE for all stored procedures in the database; CREATE, UPDATE, DELETE on tables and views in the database. The installation assigns a default user and role and sets permissions, which can be changed if required. Consult the Security section for details.

Enabling the database

The installation routine will automatically enable the database for Using CLR.