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¶
Create empty MFSQL database on SQL Server
Execute core schema scripts (tables, types, utility functions)
Deploy assemblies to
C:\MFSQL\Assemblies
(or configured path)Execute stored procedures scripts (system + context menu–related)
Import content package into the vault (via M‑Files Admin)
Configure connection string and settings in VAF
Validate using Validate and smoke tests