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

Question

Question

Moved a LF Repository Database, Got an error connecting to another database with Data_1 appended to the name

Administration
Updated November 11
asked on November 10

A customer running LF 12 moved their repository database and updated the DBMS connection. In the DBMS connection it only specifies a single database but they got an error that it could not connect to another database with an appended Data_1 on the name.

We moved the Data_1 database to the new server and it resolved the error.

I understand that some 20 years ago older versions used to use dual databases, but newer versions only specify one. I started working with LF in version 9 so never worked with a dual database system.

How did a customer running LF 12 end up this way and what can be done to consolidate to a single database?

0 0

Answer

SELECTED ANSWER
replied on November 10

Prior to version 8, the Laserfiche Server stored thumbnails in the database. When running on SQL Express (formerly known as MSDE), it would spin off expansion databases for them to manage the size limitations on the main SQL database. They'd be named <repoDBName_data_1.

After version 8, thumbnails are store on disk in the volume, but if Data DBs existed, their content was not migrated to disk and the repository continues to keep track of them and use them.

See https://support.laserfiche.com/kb/1012313/converting-a-migrated-laserfiche-8-msde-or-sql-server-express-database-for-use-with-the-full-edition-of-microsoft-sql-server  for instructions on how to remove them. Don't forget to backup all databases before running this script. 

3 0
replied on November 11

The conversion tool still exists! Perfect, we will give this a try.

0 0

Replies

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

Sign in to reply to this post.

Details
Related Posts
Loading ...