Manual installation path

Use this approach for high-security environments where the installer cannot be used on SQL, or to troubleshoot.

Includes

  • Ordered script execution plan

  • Content package import notes

  • Rollback guidance

When to use

  • Locked-down SQL Server (no installer execution)

  • Forensics and support troubleshooting

Detail Steps

Typical order of operations

  1. Create empty MFSQL database on SQL Server

  2. Execute core schema scripts (tables, types, utility functions)

  3. Deploy assemblies to C:\MFSQL\Assemblies (or configured path)

  4. Execute stored procedures scripts (system + context menu–related)

  5. Import content package into the vault (via M‑Files Admin)

  6. Configure connection string and settings in VAF

  7. Validate using Validate and smoke tests