You are viewing limited content. For full access, please sign in.

Question

Question

Database migration to newer sql server

asked on February 20, 2023

Dears,

 

We plan to transfer Laserfiche database from SQL Server v14 to SQL Server v19.

We will follow the guidance of Laserfiche of how to move LF DB to an newer SQL version, as follows

  1. Unregister each Laserfiche repository whose data will be moved to the new SQL Server.
  2. Stop the Laserfiche Server.
  3. Detach the SQL database from the current Microsoft SQL Server.
  4. Move the SQL data files (.mdf and .ldf files) corresponding to the detached SQL database to the new SQL Server.
  5. Attach the SQL database to the new SQL Server.
  6. Restart the Laserfiche Server.
  7. Register each Laserfiche repository.

 

Our question is, does this procedure create any compatibilities issue? is it safe when we plan to upgrade LF from 9.3 to 11 and therefore SQL server upgrades?

 

Please advise.

 

Thanks

0 0

Replies

replied on February 20, 2023

It looks like the last version that Laserfiche 9 was tested against was SQL 2014 (see KB). To avoid compatibility issues, I would do the following:

  1. Unregister each Laserfiche repository whose data will be moved to the new SQL Server.
  2. Stop the Laserfiche Server.
  3. Detach the SQL database from the current Microsoft SQL Server.
  4. Move the SQL data files (.mdf and .ldf files) corresponding to the detached SQL database to the new SQL Server.
  5. Attach the SQL database to the new SQL Server.
  6. Upgrade to Laserfiche Server 11.
  7. Restart the Laserfiche Server.
  8. Register each Laserfiche repository.

During the attachment process of the repositories, they will be upgraded to version 11.

1 0
replied on February 24, 2023

If you haven't already done this, I would recommend adding a step between 3 and 4 to make a back-up copy of the database files.  That way if something does go wrong in the later steps, you can still revert back if needed.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.