Vault Transfer from Firebird to SQL

Provided they're the same versions, you should be able to use the replication feature to extract the structure and content you need and move the data across.

However, there are some caveats. Particularly if you've tried to manually copy the structure of the office vault locally.

What are you trying to achieve?

Craig.

Actually, I will create a new vault from scratch at the office with SQL. Then, I will export the structure and data from the demo in my laptop which is using Firebird. Then, I will import this into the new vault at the office. I use the same versions.

In that case, using the replication (content / structure export) back to the office vault should work fine. The replication function doesn't care what back-end database/storage you use.

Craig.

Thank you very much. :)

You could also use backup on your laptop and restore on the serve and then change the vault to SQL. I have done that for a client last week moving a vault from an old Windows 2003 server to a new hosted environment with SQL. The vault had about 10 GB of file data and 1 GB of metadata. No problems even going from M-Files 9 to M-Files 2015.2 :-)

Hi,

did you have any problems migrating the database from Firebird to SQL?

I'm getting error in phase migrating tables to sql.

I suggest you contact our support department - support@m-files.com - for issues like this.

Regards,

Craig.

Hi,

okay. One question though.

I'm getting deadlocks when verifying the database (task failing) and the M-Files Indexer is taking 30 - 50% cpu.

Do I need to wait until the indexing has finished, then verify and repair the database. And after that try the migration once more...?

Thanks!

Hi,

I suggest you let M-Files support guide you. If the verification task within M-Files Admin is failing then this may be indicative of another issue, which may need to be resolved prior to a migration.

As I said: in cases like this you need our support department's input.

In the issue, note as much information as you can (M-Files version, what steps you've tried, entries from Windows Event Logs, etc.), as well as provide your company name or serial number.
Regards,

Craig.