Are there any plans to add this DB? We have a 2022 system and rolling this back to SQL 2019 is no easy task.
We have adding SQL Server 2022 support to the Repository Export Client (REC) on our list (feature #567749).
We currently expect that feature release in the first half of 2025.
Found it:
1. Convert database to SQL Server 2019
a. Use SSMS to connect to SQL Server 2022. Right click the repository database and choose Tasks -> Export Data-tier Application... This step will generate a bacpac file.
b. Use SSMS to connect to SQL Server 2019. Right click Databases and choose Import Data-tier Application... Choose the bacpac to generate a new database.
c. Back up the database in SQL Server 2019
2. Modify REC config
a. Open "C:\Program Files\Laserfiche\Repository Export Client\resources\bin\RepositoryExportClient.WebApi.exe.config", add a new key under appSettings:
<add key="SqlServerMaxVersion" value="16" />
3. Unregister the self-hosted Laserfiche repository from the Administration Console and re-register the repository using the SQL 2019 database.
4. Re-run REC in Planning mode.
I would be surprised if it doesn't support it already since the Laserfiche Cloud Migration Readiness Assessment Tool does support SQL Server 2022.
Using the Repository Export Client, it does not like SQL 2022 one bit:
Entirely separate codebases, so while that does logically make sense, the two tools/utilities are completely independent. The Assessment Tool is much newer and worked with SQL Server 2022 from the start.
It has not been supported in my last 2 recent migrations. However it only required about 1 hour to roll it back each time. I installed 2019 as an additional instance and used the instructions provided by Laserfiche to make a copy of the database on the 2019 instance before migration.
Thanks Chad - Do you have a link for that? I have had no luck so far trying a backward migration.
Found it:
1. Convert database to SQL Server 2019
a. Use SSMS to connect to SQL Server 2022. Right click the repository database and choose Tasks -> Export Data-tier Application... This step will generate a bacpac file.
b. Use SSMS to connect to SQL Server 2019. Right click Databases and choose Import Data-tier Application... Choose the bacpac to generate a new database.
c. Back up the database in SQL Server 2019
2. Modify REC config
a. Open "C:\Program Files\Laserfiche\Repository Export Client\resources\bin\RepositoryExportClient.WebApi.exe.config", add a new key under appSettings:
<add key="SqlServerMaxVersion" value="16" />
3. Unregister the self-hosted Laserfiche repository from the Administration Console and re-register the repository using the SQL 2019 database.
4. Re-run REC in Planning mode.
Thanks for digging this out. I had tried this, but ran into errors when SSMS tried to rebuild the foreign keys. I'll run it again and post the errors here. I'm doing this the slow way, exporting and reimporting the volumes into a new 2019 repo.
Is it possible you selected Extract Data Tier Application instead of Export? I did this once and I think it generated a similar error.
Yes, you are correct - I ran the data tier export and then imported it into 2019 successfully. One weird quirk, you have to remove domain accounts as they are not compatible with Azure, whether you are sending the DB to Azure or not. Thanks for the tip, this is a much cleaner way to revert back to 2019 than using volumes.
The final result:
Ah that's right. I had to remove some domain accounts once before too. Not sure what Microsoft was thinking here. In their dream, there is nothing but Azure.