Hi everyone,
I'm currently in the process of migrating a large M-Files vault from Firebird to MS SQL, but the migration keeps failing due to timeout errors. I suspect that the issue might be related to the size of the vault.
Interestingly, when I perform the migration with a brand-new vault, everything works fine. This makes me wonder if the issue is tied to the volume of data, indexing, or system performance limitations.
Has anyone encountered similar issues with large vaults during migration? Are there specific best practices, settings, or optimizations I should consider to prevent timeouts and ensure a smooth transition? Also, could the failure be related to system limitations, query execution time, or database constraints?
Any insights, troubleshooting steps, or recommendations would be greatly appreciated!
Thanks in advance.
