Question

Expansion Database Upgrade

Administration Installation and Upgrades

Updated June 15, 2016

asked on January 24, 2014

We have a customer that is still on SQL express edition of the Laserfiche server module. To recap on the exact upgrade path, we start on SQLExpress 7 and upgraded to SQLExpress 8.0, recently we upgrade from SQLExpress 8.3 to SQLExpress 9.1.

While at the Laserfiche conference, Peiter Nauta pointed me to an internal programmer (which I forgot to jot down his name) that advised the expansion databases are no longer used in 9.1. The 9.1 page location information is now stored in the volume with the pages but the old information is kept in the expansion db.

Once we re-indexed the entire repository and disabled the expansion database in SQL Manager, we noticed the thumbnail information is not longer visible.

Is there a "formal" migration process for 8 to 9.1 that we should be handling with the expansion database?

0 0

Replies

replied on January 24, 2014

The Laserfiche 8 Migration Utility typically handles the migration process; it automatically moves data from Laserfiche 7 expansion databases into the new Laserfiche 8 primary database if you choose a source MSDE/SQL Express Laserfiche 7 database and a destination full SQL Server database. Since your update path was a little different, your databases weren’t merged. To merge your primary and expansion databases, use the utility attached to knowledge base article 1012313. Make sure you back the database up before making any serious changes like this. After, you should be able to remove the expansion databases without losing your thumbnails.

0 0

replied on January 24, 2014

Thanks Zack. Will this also work for SQLExpress-9 database conversion within itself? We already upgraded the database to 9.1 at this point. We would simple like to remove the expansion databases if they are no longer needed in 9.x version of the SQL Express edition system.

0 0

replied on January 24, 2014

I'm not sure I follow. The conversion script will reorganize your database such that the expansion databases are no longer used. They are no longer necessary since you're on SQL Express 9--you don't need to change your DBMS to get rid of them.

0 0

replied on January 24, 2014

For repositories that are already on 8.0 or later, you will need to use the conversion script to get rid of the expansion databases which, as Zach noted, can be found at KB article 1012313. However, this is ONLY for scenarios where you originally used MSDE or SQL Express as your DBMS pre-8, then migrated to post-8 while still using MSDE or SQL Express and THEN are converting to full SQL. While expansion databases are not created anymore on new (post-8) SQL Express repositories, they are still needed for pre-migrated ones. You can't see thumbnail data because you've disabled the expansion database and your general database is still trying to find it there.

0 0

replied on June 9, 2014

Justin,

Do you recommend exporting all the volumes and re-importing to completely remove the links of the old expansion databases? Or would a simple volume migration work?

0 0

replied on June 9, 2014

This doesn't have anything to do with volumes, actually, so neither of your suggestions are necessary. I'm referring to the migration of the database backend - that's where the expansion databases are located and that's why, if you've already migrated the repository from version 7 or earlier, you would run the SQL script from KB Article 1012313.

0 0

replied on May 22, 2015 • Show version history

We have a similar situation and the answers above are a little ambiguous, or at least not completely clear.

We have already upgraded from 8.x to 9.0 of Avante and the Expansion databases are still there in SQL express and we are getting ready to move this DB to the Full SQL version of LF Rio.

Do we need to run the Script mentioned above on the 9.0 DB to consolidate the expansion databases? Or do we need to do something else?

Thanks in advance,

0 0

replied on May 22, 2015

You'll need to run the script from KB 1012313.

0 0

replied on June 14, 2016

Does the script from KB 1012313 work for LF 10 repositories with expansion DBs? It only states that it is for LF 8 and 9.

0 0

replied on June 14, 2016

Hi Bert,

It looks like the v10.1 db schema's internal version if 8.7.1, so yes, I'd expect this to work.

0 0

replied on June 15, 2016

Thanks

0 0

You are not allowed to follow up in this post.

Question

Question

Expansion Database Upgrade

Replies

Sign in to reply to this post.